Re: Bug: GCC riscv building fails at self-tests with specific march

2023-11-09 Thread Michael T. Kloos
x27; requires '-march' to subsume the 'M' extension It seems to be trying to build test suites that are in conflict with my march settings. Interestingly, I didn't have this issue when trying to build the release version tagged "releases/gcc-13.2.0".  However, I wanted to use some newer features that were only merged less than a month ago.  I tried to build the GIT tree and encountered this error.  I attempted to bisect the issue and found that it only happens when "gcc/DEV-PHASE" is set to: experimental I'm not very familar with GCC's build system, but this suggests to me that the tests are only conditionally built on experimental/development codebase snapshots.  Michael T. Kloos

Bug: GCC riscv building fails at self-tests with specific march

2023-11-09 Thread Michael T. Kloos
e 'M' extension cc1plus: error: '-mdiv' requires '-march' to subsume the 'M' extension It seems to be trying to build test suites that are in conflict with my march settings. Interestingly, I didn't have this issue when trying to build the release version tagged "releases/gcc-13.2.0".  However, I wanted to use some newer features that were only merged less than a month ago.  I tried to build the GIT tree and encountered this error.  I attempted to bisect the issue and found that it only happens when gcc/DEV-PHASE is set to: experimental I'm not very familar with GCC's build system, but this suggests to me that the tests are only conditionally built on experimental/development codebase snapshots.  Michael T. Kloos

RE: Debugging information in C macros

2011-05-10 Thread Michael T
> From: rasel...@hotmail.com > > From: bas...@starynkevitch.net > > On Tue, 10 May 2011 17:33:57 +0200 > > Michael T wrote: > > > I was wondering if it is possible to improve the debugging information > > > generated by gcc when resolving C macros? Just a

RE: Debugging information in C macros

2011-05-10 Thread Michael T
> From: bas...@starynkevitch.net > On Tue, 10 May 2011 17:33:57 +0200 > Michael T wrote: > > I was wondering if it is possible to improve the debugging information > > generated by gcc when resolving C macros? Just as an example, when I > > preprocessed the following

Debugging information in C macros

2011-05-10 Thread Michael T
Hello all, I was wondering if it is possible to improve the debugging information generated by gcc when resolving C macros? Just as an example, when I preprocessed the following C file: extern int printf (__const char *__restrict __format, ...); #define my_macro(i) \   do { \     *(i) = 1; \