Re: Preventing warnings

2007-01-20 Thread Andrew Pinski
On Sun, 2007-01-21 at 01:49 -0500, Richard Stallman wrote: > It would be nice to have such a construct in GNU C, something that > could be used in a macro expansion, and would turn off _all_ warnings > for the code within the construct. http://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Pragmas.html Bu

Re: Preventing warnings

2007-01-20 Thread Richard Stallman
Nevertheless, I (and others seem to agree) would like to name that particular warning, so it can be enabled/disabled. Also, there is a similar warning for unsigned >= 0 and unsigned < 0 in -Wextra. There are bug reports about the inconsistency (http://gcc.gnu.org/PR23587). So,

Re: Top level libgcc checked in

2007-01-20 Thread Andreas Schwab
Rask Ingemann Lambertsen <[EMAIL PROTECTED]> writes: > Checking multilib configuration for libgcc... > Configuring in ia16-elf/libgcc > [snip] > checking whether decimal floating point is supported... no > *** Configuration ia16-unknown-elf not supported > make[1]: *** [configure-target-libgcc] Fe

Re: Top level libgcc checked in

2007-01-20 Thread Rask Ingemann Lambertsen
On Wed, Jan 03, 2007 at 11:28:29PM -0500, Daniel Jacobowitz wrote: > I've just committed the approved top level libgcc patches, which > create a top level "libgcc" directory. I updated to revision 120997 for my Intel x86 16-bit port, to find: Checking multilib configuration for libgcc... Confi

Re: Running GCC tests on installed compiler

2007-01-20 Thread Dominique Dhumieres
Gerald, > > This script seems quite outdated: it tests g77 and not gfortran, even > > with the latest 4.3.0 snapshot (20070112). ... > > Would you mind submitting this as a patch? --- gcc-4.3-20070120/contrib/test_installed Fri Jul 11 08:05:01 2003 +++ gcc-4.

Compiling libgcc functions with non-default LIBGCC2_UNITS_PER_WORD

2007-01-20 Thread Rask Ingemann Lambertsen
Somewhere in the libgcc build machinery, there is mechanism to override the default LIBGCC2_UNITS_PER_WORD setting when compilng a function, so you could in principle provide e.g. _divsi3 as well as _divdi3. It there a way of making use of this facility in a more elegant way than putting the who

Re: trying to fix a bug in m6812 front-end

2007-01-20 Thread Rask Ingemann Lambertsen
On Fri, Jan 19, 2007 at 05:10:27PM -0700, Sean D'Epagnier wrote: > I am using gcc 3.3.5 with the latest m68hc1x patches to compile programs for a > 9s12 processor, and cc1 calls abort when compiling the following code: It would be most useful to have the exact error message. I'm guessing that t