From: Max Lawson <mlawson@drfmc.ceng.cea.fr>
To: robertl@dgii.com, khan@xraylith.wisc.edu
Cc: Theodore.Papadopoulo@sophia.inria.fr, egcs@cygnus.com
Subject: Re: Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
Date: Mon, 01 Dec 1997 17:20:00 -0000 [thread overview]
Message-ID: <9712012253.AA29437@drfmc.ceng.cea.fr> (raw)
Maybe, we should post assembly and/or preprocessed outputs for
a given test-case compiled with given options. This way s.o. :-) could
have a look... Could s.o. post an adequate test ?
Regards, Max
next reply other threads:[~1997-12-01 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-01 17:20 Max Lawson [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-12-01 7:38 egcs-971127: testsuite results on i586-pc-linux-gnulibc1 Theodore Papadopoulo
1997-12-01 11:03 ` Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1] Mumit Khan
1997-12-01 11:33 ` Robert Lipe
1997-12-01 19:30 ` Mumit Khan
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=9712012253.AA29437@drfmc.ceng.cea.fr \
--to=mlawson@drfmc.ceng.cea.fr \
--cc=Theodore.Papadopoulo@sophia.inria.fr \
--cc=egcs@cygnus.com \
--cc=khan@xraylith.wisc.edu \
--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).