public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Segher Boessenkool <segher@koffie.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/7726: Fails to produce the correct  implementation-dependantoutput for loop optimization under x86 ->  optimizes away a loop that shouldcomplete
Date: Sun, 29 Dec 2002 19:16:00 -0000	[thread overview]
Message-ID: <20021230031600.18355.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/7726; it has been noted by GNATS.

From: Segher Boessenkool <segher@koffie.nl>
To: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
Cc: bangerth@dealii.org, carlos@baldric.uwo.ca, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/7726: Fails to produce the correct 
 implementation-dependantoutput for loop optimization under x86 -> 
 optimizes away a loop that shouldcomplete
Date: Sun, 29 Dec 2002 13:22:39 +0100

 Falk Hueffner wrote:
 > 
 > On 6 Dec 2002 bangerth@dealii.org wrote:
 > 
 > > Hm, the code goes into an endless loop on my system also without
 > > optimization and with all the compilers I have (i.e. gcc2.95, 3.0,
 > > 3.2, 3.2.2pre, 3.3pre, and icc7). Are you sure that the overflow you
 > > are exploiting is really defined in ISO C?
 > 
 > Reading the value of a union member other than the last one stored into is
 > undefined (at least in C99),
 
 Implementation defined, actually...
 
 > so it could be easily argued that this is not
 > a bug. However, gcc seems to support this in some other places (see the
 > info entry about aliasing). So IMHO this should either be "fixed", or it
 > should be documented exactly which union type punning tricks are OK.
 
 ...and implementation defined bahaviour should be documented.  And it is,
 even: there is some discussion of this in the manual, under "-fstrict-aliasing",
 stating that with GCC, type-punning via unions is explicitly allowed.
 
 
 Segher
 


                 reply	other threads:[~2002-12-30  3:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021230031600.18355.qmail@sources.redhat.com \
    --to=segher@koffie.nl \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).