From: Diego Novillo <dnovillo@redhat.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: Some tests in gcc.c-torture rely on undefined behaviour?
Date: Tue, 12 Jul 2005 18:47:00 -0000 [thread overview]
Message-ID: <20050712184618.GA6309@topo.toronto.redhat.com> (raw)
In-Reply-To: <m3r7e3kgx5.fsf@gossamer.airs.com>
On Tue, Jul 12, 2005 at 11:39:18AM -0700, Ian Lance Taylor wrote:
> I would guess that 920612-1.c, at least, could just be changed to use
> unsigned int, and it would continue to test whatever bug it was
> testing when it was originally added.
>
The problem is somewhat more widespread now with the tree
optimizers. In particular with old test cases. Some of these
cases are essentially optimized into empty functions by the time
we get into the RTL passes.
We would have to audit them all and add enough external
functions, volatile markers or what-have-you to have them survive
until RTL. Not sure if it's worth it.
next prev parent reply other threads:[~2005-07-12 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 14:41 Nicholas Nethercote
2005-07-12 16:45 ` Joe Buck
2005-07-12 16:47 ` Joseph S. Myers
2005-07-12 18:39 ` Ian Lance Taylor
2005-07-12 18:47 ` Diego Novillo [this message]
2005-07-12 18:50 ` Ian Lance Taylor
2005-07-13 3:47 ` Nicholas Nethercote
2005-07-13 19:58 ` Robert Dewar
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=20050712184618.GA6309@topo.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
--cc=joseph@codesourcery.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).