-print-* command-line switches misbehave or are misdocumented

Some of the -print-* command-line switches either don't work as advertised or their documentation should be made more clear. All of the examples below are with the following version of GCC: gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5) Copyright (C) 2006 Free Software Foundation, Inc. This

gtyp-input.list should contain absolute paths.

Hello all, gengtype how has a plugin mode (when invoked with -p as the first program argument after gengtype). It would be much easier for plugins if gtyp-input.list contained only absolute paths. In my case, (AMD64/Debian/Sid), it contains only two relative filepaths: auto-host.h & options.

VTA compile time memory usage comparison

On Mon, Jun 08, 2009 at 01:35:34PM -0400, Diego Novillo wrote: > On Sun, Jun 7, 2009 at 16:04, Alexandre Oliva wrote: > > > So the question is, what should I measure?  Memory use for any specific > > set of testcases, summarized over a bootstrap with memory use tracking > > enabled, something else

Re: GCC build failure, h...@149166 on native

On Thu, Jul 2, 2009 at 5:23 PM, Paolo Bonzini wrote: > Well, if the failure is in libgcc, that means that we get a mail on every > commit.  In this case my patch went in on Sunday afternoon, and the problems > were fixed only on Thursday for multiple reasons (multiple patches, need for > approval,

Re: GCC build failure, h...@149166 on native

What is wrong about failures being annoying? Paolo, you could have reverted your original patch and worked with the PowerPC developers to test a revised patch. If I had been asked, I would have. Paolo

Re: gtyp-input.list should contain absolute paths.

Hello Basile, * Basile STARYNKEVITCH wrote on Fri, Jul 03, 2009 at 12:10:17PM CEST: > It would be much easier for plugins if gtyp-input.list contained > only absolute paths. In my case, (AMD64/Debian/Sid), it contains > only two relative filepaths: auto-host.h & options.h Over here it contains on

Re: Endianess attribute

On Thu, Jul 02, 2009 at 06:54:52PM -0400, Ken Raeburn wrote: > On Jul 2, 2009, at 16:44, Michael Meissner wrote: >> Anyway I had some time during the summit, and I decided to see how >> hard it >> would be to add explicit big/little endian support to the powerpc >> port. It >> only took a few

Re: gtyp-input.list should contain absolute paths.

Ralf Wildenhues wrote: Hello Basile, * Basile STARYNKEVITCH wrote on Fri, Jul 03, 2009 at 12:10:17PM CEST: It would be much easier for plugins if gtyp-input.list contained only absolute paths. In my case, (AMD64/Debian/Sid), it contains only two relative filepaths: auto-host.h & options.h

Re: GCC build failure, h...@149166 on native

On Fri, 2009-07-03 at 07:43 +0200, Paolo Bonzini wrote: > On 07/03/2009 07:31 AM, Eric Botcazou wrote: > >> This was pretty bad, but it was also unlucky that the failure was only > >> on the exact arch that the tester builds for. Failures on powerpc are > >> extremely annoying, failures on SPARC w

Re: GCC build failure, h...@149166 on native

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 03/07/2009 15:58, Laurent GUERBY a écrit : [...] > Right now the bootstrap+check loops I run on the compile farm cover the > following *-linux platforms with c,ada unless otherwise specified: > > gcc13 x86_64trunk 3h30 > gcc15 x86_644.4

g-socket.adb error

Hi, Apparently no one has hit this case. RTEMS does not have two error codes that g-socket.adb maps back. From s-oscons.ads: ESHUTDOWN : constant := -1; -- Cannot send once shutdown ESOCKTNOSUPPORT : constant := -1; -- Socket type not supported This res

Is there any pointers you might have What are the pros and cons I should be looking out for Any info much appreciated Thank you very much John

Hi, Is there any pointers you might havewhat are the pros and cons i should be looking out for any info much appreciatedthank you very muchjohn? What Gotchas should I be aware of? Any help appreciated. Thank you so much. Regards, Joan