search for: noret

Displaying 17 results from an estimated 17 matches for "noret".

Did you mean: noreg
2010 Nov 08
2
[LLVMdev] Creating tablegen patterns for intrinsics with no return value.
...with no return value and I need to match them to machine instructions. If the instruction has a return value I am able to correctly match it, but if I try to create some tablegen code that has no return value, the instruction gets deleted. Here is my profile/node/pattern. Profile: def SDTIL_BinAtomNoRet : SDTypeProfile<0, 3, [ SDTCisPtrTy<0>, SDTCisVT<1, i32>, SDTCisVT<2, i32> ]>; Node: def atom_g_add_noret : SDNode<"AMDILISD::ATOM_G_ADD_NORET", SDTIL_BinAtomNoRet, [SDNPHasChain]>; Pattern: def ATOM_G_ADD_NORET : BinAtomNoRet<IL_OP_UAV_ADD,...
2010 Nov 08
1
[LLVMdev] Creating tablegen patterns for intrinsics with no return value.
...ttern should > suffice to tell the compiler that there's more going on than it can > detect just by looking at the inputs and outputs, and so it won't > delete the instruction. Something like the following should do the > trick: > let hasSideEffects = 1 in > def ATOM_G_ADD_NORET : BinAtomNoRet<IL_OP_UAV_ADD, > "_id($id)", atom_g_add_noret>; > > For an existing example, have a look at the memory barrier instruction > definitions for the ARM target (DMB and DMB_MCR in ARMInstrInfo.td). > > Regards, > Jim [Villmow, Micah] Jim...
2010 Nov 08
0
[LLVMdev] Creating tablegen patterns for intrinsics with no return value.
...1" to your instruction pattern should suffice to tell the compiler that there's more going on than it can detect just by looking at the inputs and outputs, and so it won't delete the instruction. Something like the following should do the trick: let hasSideEffects = 1 in def ATOM_G_ADD_NORET : BinAtomNoRet<IL_OP_UAV_ADD, "_id($id)", atom_g_add_noret>; For an existing example, have a look at the memory barrier instruction definitions for the ARM target (DMB and DMB_MCR in ARMInstrInfo.td). Regards, Jim > > Here is my profile/node/pattern. > Prof...
2019 May 19
2
Race condition on parallel package's mcexit and rmChild
...ry rarely, I did notice "ignoring SIGPIPE signal" error every now and then. After a deep dig into the source code, I think I found something worth noticing. In short, wring to pipe in the C function mc_exit(SEXP sRes) may cause a SIGPIPE. Code from src/library/parallel/src/fork.c: SEXP NORET mc_exit(SEXP sRes) { int res = asInteger(sRes); ... ... if (master_fd != -1) { /* send 0 to signify that we're leaving */ size_t len = 0; /* assign result for Fedora security settings */ ssize_t n = write(master_fd, &len, sizeof(len)); ... ... } So a pipe wr...
2025 Jan 15
1
Build error with gcc 15
On 15/01/2025 16:06, I?aki Ucar wrote: > Dear R Core, > > GCC 15 is already in Fedora rawhide, because it will be part of the next > release, Fedora 42. R 4.4.2 fails to build with the following error [1]: > >> sys-std.c:1189:1: warning: ?noreturn? attribute ignored [-Wattributes] >> 1189 | void Rstd_CleanUp(SA_TYPE saveact, int status, int runLast) >> | ^~~~ >> sys-std.c:1189:1: error: expected identifier or ?(? before ?void? You failed to say that GCC 15 defaults to C23 (and they have not yet documented that...
2019 May 20
1
Race condition on parallel package's mcexit and rmChild
...ery now and then. > > After a deep dig into the source code, I think I found something worth > > noticing. > > > > In short, wring to pipe in the C function mc_exit(SEXP sRes) may cause > > a SIGPIPE. Code from src/library/parallel/src/fork.c: > > > > SEXP NORET mc_exit(SEXP sRes) > > { > > int res = asInteger(sRes); > > ... ... > > if (master_fd != -1) { /* send 0 to signify that we're leaving */ > > size_t len = 0; > > /* assign result for Fedora security settings */ > > s...
2019 May 20
0
Race condition on parallel package's mcexit and rmChild
...ry rarely, I did notice "ignoring SIGPIPE signal" error every now and then. After a deep dig into the source code, I think I found something worth noticing. In short, wring to pipe in the C function mc_exit(SEXP sRes) may cause a SIGPIPE. Code from src/library/parallel/src/fork.c: SEXP NORET mc_exit(SEXP sRes) { int res = asInteger(sRes); ... ... if (master_fd != -1) { /* send 0 to signify that we're leaving */ size_t len = 0; /* assign result for Fedora security settings */ ssize_t n = write(master_fd, &len, sizeof(len)); ... ... } So a pipe wr...
2019 May 20
0
Race condition on parallel package's mcexit and rmChild
...oring SIGPIPE signal" error every now and then. > After a deep dig into the source code, I think I found something worth > noticing. > > In short, wring to pipe in the C function mc_exit(SEXP sRes) may cause > a SIGPIPE. Code from src/library/parallel/src/fork.c: > > SEXP NORET mc_exit(SEXP sRes) > { > int res = asInteger(sRes); > ... ... > if (master_fd != -1) { /* send 0 to signify that we're leaving */ > size_t len = 0; > /* assign result for Fedora security settings */ > ssize_t n = write(master_fd, &le...
2025 Jan 15
1
Build error with gcc 15
Dear R Core, GCC 15 is already in Fedora rawhide, because it will be part of the next release, Fedora 42. R 4.4.2 fails to build with the following error [1]: > sys-std.c:1189:1: warning: ?noreturn? attribute ignored [-Wattributes] > 1189 | void Rstd_CleanUp(SA_TYPE saveact, int status, int runLast) > | ^~~~ > sys-std.c:1189:1: error: expected identifier or ?(? before ?void? I've seen some references to this in the source code, so this may be fixed in R devel. If this...
2019 Jul 13
2
Mitigating Stalls Caused by Call Deparse on Error
...R_GetTraceback + R_GetTracebackParsed ? R_GetVarLocSymbol ? R_GetVarLocValue ? R_HandlerStack Index: src/include/Defn.h =================================================================== --- src/include/Defn.h?? ?(revision 76827) +++ src/include/Defn.h?? ?(working copy) @@ -1296,6 +1296,7 @@ ?void NORET ErrorMessage(SEXP, int, ...); ?void WarningMessage(SEXP, R_WARNING, ...); ?SEXP R_GetTraceback(int); +SEXP R_GetTracebackParsed(int); ? ?R_size_t R_GetMaxVSize(void); ?void R_SetMaxVSize(R_size_t); Index: src/library/base/R/traceback.R ===============================================================...
2019 Apr 24
2
R problems with lapack with gfortran
...ind problem areas. There are quite a few warnings that were flagged, due to mismatches in function types. The prototypes that R has in its header files, for example BLAS.h, are often not compatible with gfortran function declarations. To take one small example, in src/main/print.c, we have void NORET F77_NAME(xerbla)(const char *srname, int *info) so xerbla_ is defined with two arguments. However, gfortran passes string lengths as hidden arguments. You can see this by compiling the small example $ cat xer.f SUBROUTINE FOO INTEGER INFO CALL XERBLA ('FOO', INFO)...
2024 Jul 29
1
Minor inconsistencies in tools:::funAPI()
Hi Ivan Can you please clarify what input files should be used with your proposed function? I tried a few files in r-svn/src/include and one of them gave me an error. > getdecl("~/R/r-svn/src/include/R.h") [1] "R_FlushConsole" "R_ProcessEvents" "R_WaitEvent" > getdecl("~/R/r-svn/src/include/Rdefines.h") Error in regmatches(lines,
2019 Jul 14
2
[External] Mitigating Stalls Caused by Call Deparse on Error
...R_GetVarLocSymbol > ? R_GetVarLocValue > ? R_HandlerStack > Index: src/include/Defn.h > =================================================================== > --- src/include/Defn.h?? ?(revision 76827) > +++ src/include/Defn.h?? ?(working copy) > @@ -1296,6 +1296,7 @@ > ?void NORET ErrorMessage(SEXP, int, ...); > ?void WarningMessage(SEXP, R_WARNING, ...); > ?SEXP R_GetTraceback(int); > +SEXP R_GetTracebackParsed(int); > ? > ?R_size_t R_GetMaxVSize(void); > ?void R_SetMaxVSize(R_size_t); > Index: src/library/base/R/traceback.R > =======================...
2019 Jul 16
1
[External] Mitigating Stalls Caused by Call Deparse on Error
...R_HandlerStack >>> Index: src/include/Defn.h >>> =================================================================== >>> --- src/include/Defn.h (revision 76827) >>> +++ src/include/Defn.h (working copy) >>> @@ -1296,6 +1296,7 @@ >>> void NORET ErrorMessage(SEXP, int, ...); >>> void WarningMessage(SEXP, R_WARNING, ...); >>> SEXP R_GetTraceback(int); >>> +SEXP R_GetTracebackParsed(int); >>> >>> R_size_t R_GetMaxVSize(void); >>> void R_SetMaxVSize(R_size_t); >>> Index: src...
2019 Jul 14
0
[External] Mitigating Stalls Caused by Call Deparse on Error
...R_GetVarLocSymbol > ? R_GetVarLocValue > ? R_HandlerStack > Index: src/include/Defn.h > =================================================================== > --- src/include/Defn.h?? ?(revision 76827) > +++ src/include/Defn.h?? ?(working copy) > @@ -1296,6 +1296,7 @@ > ?void NORET ErrorMessage(SEXP, int, ...); > ?void WarningMessage(SEXP, R_WARNING, ...); > ?SEXP R_GetTraceback(int); > +SEXP R_GetTracebackParsed(int); > ? > ?R_size_t R_GetMaxVSize(void); > ?void R_SetMaxVSize(R_size_t); > Index: src/library/base/R/traceback.R > =======================...
2019 Jul 15
0
[External] Mitigating Stalls Caused by Call Deparse on Error
...etVarLocValue >> ? R_HandlerStack >> Index: src/include/Defn.h >> =================================================================== >> --- src/include/Defn.h?? ?(revision 76827) >> +++ src/include/Defn.h?? ?(working copy) >> @@ -1296,6 +1296,7 @@ >> ?void NORET ErrorMessage(SEXP, int, ...); >> ?void WarningMessage(SEXP, R_WARNING, ...); >> ?SEXP R_GetTraceback(int); >> +SEXP R_GetTracebackParsed(int); >> ? >> ?R_size_t R_GetMaxVSize(void); >> ?void R_SetMaxVSize(R_size_t); >> Index: src/library/base/R/traceback.R...
2019 May 03
0
R problems with lapack with gfortran
...te a few warnings that were flagged, due to mismatches > in function types. > > The prototypes that R has in its header files, for example BLAS.h, > are often not compatible with gfortran function declarations.? To take > one small example, in src/main/print.c, we have > > void NORET F77_NAME(xerbla)(const char *srname, int *info) > > so xerbla_ is defined with two arguments. > > However, gfortran passes string lengths as hidden arguments. > You can see this by compiling the small example > > $ cat xer.f > ????? SUBROUTINE FOO > ????? INTEGER INFO &gt...