Re: GCC 4.2 branch comparision failure building Java

Paolo Bonzini wrote: > Mark Mitchell wrote: >> Paolo Bonzini wrote: >> >>> IIUC, the problem only manifests while *building* the release candidates, >>> not for users of the release candidate. >>> >>> For 4.2, my suggestion is to just use a bootstrap4 while building the RC. >> That's an attractive

Re: GCC 4.2 branch comparision failure building Java

Mark Mitchell wrote: > Paolo Bonzini wrote: > >> IIUC, the problem only manifests while *building* the release candidates, >> not for users of the release candidate. >> >> For 4.2, my suggestion is to just use a bootstrap4 while building the RC. > > That's an attractive idea. But, I'd rather fix

Re: GCC 4.2 branch comparision failure building Java

Paolo Bonzini wrote: For 4.3, we can use --enable-stage1-languages=all when building the RCs. I can prepare a patch to do that automatically when --enable-generated-files-in-srcdir is passed. That should not be needed on the trunk, as the .y files in question (gcc/java/parse.y and gcc/java/

Re: GCC 4.2 branch comparision failure building Java

Paolo Bonzini wrote: > IIUC, the problem only manifests while *building* the release candidates, > not for users of the release candidate. > > For 4.2, my suggestion is to just use a bootstrap4 while building the RC. That's an attractive idea. But, I'd rather fix it correctly, because distribut

Re: GCC 4.2 branch comparision failure building Java

On Fri, 16 Mar 2007, Mark Mitchell wrote: > I was thinking about trying to fix this by doing something similar -- > but avoiding the copy. You still need the srcextra rule around to do the copy, for use in generating gcc.pot without --egfis - or the regeneration instructions could change to req

Re: GCC 4.2 branch comparision failure building Java

> This didn't apply with 4.1 because then, without toplevel bootstrap, all > files to be copied to the source directory were generated and copied in > stage 1, so stage 2 and stage 3 both built them from the source directory. > Now, stage 1 is not only built as C only but the whole stage 1 bui

Re: GCC 4.2 branch comparision failure building Java

Mark Mitchell <[EMAIL PROTECTED]> writes: > Ian Lance Taylor wrote: > > "Joseph S. Myers" <[EMAIL PROTECTED]> writes: > > > >> This is caused by --enable-generated-files-in-srcdir, as used by the > >> release script, hence not being seen by people configuring normally > >> without that option.

Re: GCC 4.2 branch comparision failure building Java

Ian Lance Taylor wrote: > "Joseph S. Myers" <[EMAIL PROTECTED]> writes: > >> This is caused by --enable-generated-files-in-srcdir, as used by the >> release script, hence not being seen by people configuring normally >> without that option. Thanks for the analysis! > Since we require GNU make,

Re: GCC 4.2 branch comparision failure building Java

"Joseph S. Myers" <[EMAIL PROTECTED]> writes: > This is caused by --enable-generated-files-in-srcdir, as used by the > release script, hence not being seen by people configuring normally > without that option. The first time Java is built (stage 2), the file > java/parse.c is generated in the

Re: GCC 4.2 branch comparision failure building Java

On Tue, 13 Mar 2007, Mark Mitchell wrote: > The GCC 4.2.0 RC1 build has failed (on x86_64-unknown-linux-gnu) with: > > Comparing stages 2 and 3 > Bootstrap comparison failure! > ./java/parse.o differs > ./java/parse-scan.o differs This is caused by --enable-generated-files-in-srcdir, as used by

Re: GCC 4.2 branch comparision failure building Java

On Thu, Mar 15, 2007 at 05:48:12PM -0700, Joe Buck wrote: > At one point I considered trying a search to see which files get > miscompiled, by combining stage1 object files from a run with 3.2.3 and > 3.4.2 and trying to do the rest of the bootstrap with that, then varying > which .o files come fro

Re: GCC 4.2 branch comparision failure building Java

On Thu, Mar 15, 2007 at 05:30:48PM -0700, Mark Mitchell wrote: > Joe Buck wrote: > > >> For what it's worth, I bootstrapped on a few different GNU/Linux > >> systems with different kernels and base compilers. I only saw > >> bootstrap comparison failures on one; that one was running Red Hat 9 > >

Re: GCC 4.2 branch comparision failure building Java

Joe Buck wrote: >> For what it's worth, I bootstrapped on a few different GNU/Linux >> systems with different kernels and base compilers. I only saw >> bootstrap comparison failures on one; that one was running Red Hat 9 >> and had gcc 3.2.2 installed in /usr/bin. On that one, a bootstrap4 >> wo

Re: GCC 4.2 branch comparision failure building Java

On Thu, Mar 15, 2007 at 04:11:29PM -0700, Ian Lance Taylor wrote: > "Joseph S. Myers" <[EMAIL PROTECTED]> writes: > > > On Tue, 13 Mar 2007, Mark Mitchell wrote: > > > > > The GCC 4.2.0 RC1 build has failed (on x86_64-unknown-linux-gnu) with: > > > > > > Comparing stages 2 and 3 > > > Bootstrap

Re: GCC 4.2 branch comparision failure building Java

"Joseph S. Myers" <[EMAIL PROTECTED]> writes: > On Tue, 13 Mar 2007, Mark Mitchell wrote: > > > The GCC 4.2.0 RC1 build has failed (on x86_64-unknown-linux-gnu) with: > > > > Comparing stages 2 and 3 > > Bootstrap comparison failure! > > ./java/parse.o differs > > ./java/parse-scan.o differs > >

Re: GCC 4.2 branch comparision failure building Java

Joseph S. Myers wrote: > On Tue, 13 Mar 2007, Mark Mitchell wrote: > >> The GCC 4.2.0 RC1 build has failed (on x86_64-unknown-linux-gnu) with: >> >> Comparing stages 2 and 3 >> Bootstrap comparison failure! >> ./java/parse.o differs >> ./java/parse-scan.o differs >> >> Has anyone else seen this? >

Re: GCC 4.2 branch comparision failure building Java

On Tue, 13 Mar 2007, Mark Mitchell wrote: > The GCC 4.2.0 RC1 build has failed (on x86_64-unknown-linux-gnu) with: > > Comparing stages 2 and 3 > Bootstrap comparison failure! > ./java/parse.o differs > ./java/parse-scan.o differs > > Has anyone else seen this? I'm now looking at this (or at a

GCC 4.2 branch comparision failure building Java

The GCC 4.2.0 RC1 build has failed (on x86_64-unknown-linux-gnu) with: Comparing stages 2 and 3 Bootstrap comparison failure! ./java/parse.o differs ./java/parse-scan.o differs Has anyone else seen this? -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713