This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
> > On Mon, Jan 23, 2006 at 03:28:59PM -0500, Andrew Pinski wrote: > > > > > > On Mon, Jan 23, 2006 at 03:16:56PM -0500, Andrew Pinski wrote: > > > > > > > > > > That's the genextract crash that rth is seeing on ppc-linux. Can you also > > > > > reproduce the ppc-darwin genautomata crash? > > > > > > > > Nope. genautomata just works. > > > > > > Clarification please. In a cross configuration targeting ppc-darwin, genextract > > > crashes and genautomata just works? Or, in a cross configuration targeting > > > ppc-linux, genextract crashes and genautomata just works? Or what? > > > > in a cross to targetting powerpc-darwin, genextract crashes and genautomata works. > > > > Should I also see what happens for powerpc-linux? > > If you can, that would be helpful. The same thing happens targetting powerpc-linux in that genextract crashes and genautomata works. > > Also, if you have access to valgrind (I can't remember if it works on x86-64 yet?) > you could run both programs under it and report what it says, since this seems > to be a bad-memory-access issue. The output might be huge - maybe best to take > that to private mail. Yes valgrind works on x86_64. The output is not that huge, it is only 17k. Attached is the output. Thanks, Andrew Pinski
Attachment:
t.txt
Description: ASCII text
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |