From: Jeffrey A Law <law@cygnus.com>
To: Robert Lipe <robertl@dgii.com>
Cc: egcs@cygnus.com
Subject: Re: disturbing g++ 971031 results. defer-pop to blame?
Date: Sun, 02 Nov 1997 19:06:00 -0000 [thread overview]
Message-ID: <15667.878524611@hurl.cygnus.com> (raw)
In-Reply-To: <19971102142810.21992@dgii.com>
In message < 19971102142810.21992@dgii.com >you write:
> I'm seeing different failures on g++ than I have before. ELF and COFF
> used to fail identically. Since it's sort of wierd, I should confess
> that ELF on this target uses dwarf2eh and COFF uses sjlj.
Yup. But, aside from the tests that actually test EH, I would expect
the run for ELF & COFF to be identical.
Did we ever come to a resolution of the multilib testing problem?
> If I hand-compile and run, say, template.9.C, I see the "PASS" output
> followed by an 'illegal instruction. Core dumped'. Even if I modify
> the assembly output for that file to just make main return, I get the
> same. I tried a couple of tests manually and got similar results.
Makes me wonder if something is goof-ing in the finalization code.
Can you debug it?
>
> If I add '-defer-pop' to most of the cases I've tried by hand, it
> seems to work. In fact, I just wrote a script to loop through those
> cases and with -defer-pop. With -defer-pop, 8 of them pass. Without
> -defer-pop, none of them pass.
Don't you mean -fno-defer-pop?
jeff
next prev parent reply other threads:[~1997-11-02 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-01 20:49 GCC 971031 on OpenServer Robert Lipe
1997-11-02 12:48 ` disturbing g++ 971031 results. defer-pop to blame? Robert Lipe
1997-11-02 19:06 ` Jeffrey A Law [this message]
1997-11-02 20:47 ` Robert Lipe
1997-11-02 22:44 ` Jeffrey A Law
1997-11-02 23:32 ` Robert Lipe
1997-11-03 2:06 ` Jeffrey A Law
1997-11-03 2:06 ` Robert Lipe
1997-11-03 1:51 ` Jeffrey A Law
1997-11-03 3:21 ` Andreas Schwab
1997-11-03 9:43 ` Robert Lipe
[not found] ` <16810.878541954.cygnus.egcs@hurl.cygnus.com>
1997-11-03 2:28 ` Jason Merrill
1997-11-03 9:43 ` disturbing g++ 971031 results. defer-pop not to blame Robert Lipe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15667.878524611@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=robertl@dgii.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).