MPI_T_source_get_timestamp(3)

💖 NAME 💖

okay bestie, gather round — MPI_T_source_get_timestamp is the moment. It returns a current timestamp from the source identified by the source_index argument. that's the whole vibe. it's giving "what time is it on that specific source, bestie?" ⏰✨

---

🌸 SYNOPSIS 🌸

int MPI_T_source_get_timestamp(int source_index, MPI_Count *timestamp)

---

🎀 INPUT PARAMETERS 🎀

• source_index — the index of the source (an integer). it's literally just which source you're talking to, bestie. point at it and go 💅

---

🦋 OUTPUT PARAMETERS 🦋

• timestamp — the current timestamp from the specified source (an integer). your prize. your little time-stampy treasure. 🫶

---

🔥 THREAD AND INTERRUPT SAFETY 🔥

okay so this one is thread-safe — and that is not a drill, that's a slay. It means this routine can be safely used by multiple threads at the same time, and nobody needs to bring their own user-provided thread locks. no lock drama, no gatekeeping, we're all welcome. 😌✨

BUT. and this is the important but — it is not interrupt safe. 😭 typically, that's because of memory allocation routines like malloc, or other non-MPICH runtime routines, that are themselves not interrupt-safe. so like, don't come for it with signals mid-alloc, iykyk. 💀

---

💜 ERRORS 💜

so here's the tea, and it applies to basically everything: all MPI routines (except MPI_Wtime and MPI_Wtick) return an error value — C routines as the value of the function, and Fortran routines in the last argument. 🌈 Before that value gets handed back to you, the current MPI error handler is called. By default? this error handler aborts the MPI job. no cap, it just ends it. 💀

Good news: the error handler can be changed:

• MPI_Comm_set_errhandler — for communicators
• MPI_File_set_errhandler — for files
• MPI_Win_set_errhandler — for RMA windows

Also MPI_Errhandler_set, that MPI-1 routine, may be used — but its use is deprecated, so like, maybe don't? 🥴 And you can use the predefined error handler MPI_ERRORS_RETURN to cause error values to be returned instead of the whole job getting nuked.

⚠️ big caveat bestie: MPI does not guarantee that an MPI program can continue past an error. however, MPI implementations will attempt to continue whenever possible. so it's giving "we'll try our best" energy, not "we promise" energy. 🙈

Now the error codes themselves, one by one, no skipping, periodt:

• MPI_SUCCESS — no error; the MPI routine completed successfully. the dream. the icon. 👑
• MPI_T_ERR_INVALID — invalid use of the interface, or bad parameter value(s). you did a little whoopsie in the args. 😬
• MPI_T_ERR_INVALID_INDEX — the index is invalid or has been deleted. it's gone, bestie, she left. 🦋
• MPI_T_ERR_NOT_INITIALIZED — the MPI tool information interface is not initialized. you gotta turn it on first, babes!! 🔌
• MPI_ERR_OTHER — other error; use MPI_Error_string to get more information about this error code. the catch-all, the mysterious one, use the lookup. 🕵️♀️

---

and that's the whole page, bestie, you ate. 💅✨

sign-off time: this lil masterpiece lives in the MPI manual, dated 4/10/2026, and yes it's MPI_T_source_get_timestamp(3) — remember her name. 🎀💖🦋