public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8300: [3.2/3.3/3.4 regression] [sparc] ICE in gen_reg_rtx, at emit-rtl.c:662 Date: Mon, 17 Mar 2003 15:36:00 -0000 [thread overview] Message-ID: <20030317153601.8995.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1420 bytes --] The following reply was made to PR optimization/8300; it has been noted by GNATS. From: Andreas Schwab <schwab@suse.de> To: Robert Schiele <rschiele@uni-mannheim.de> Cc: Richard Henderson <rth@redhat.com>, gcc-bugs@gcc.gnu.org, tneumann@pi3.informatik.uni-mannheim.de, gcc-gnats@gcc.gnu.org Subject: Re: optimization/8300: [3.2/3.3/3.4 regression] [sparc] ICE in gen_reg_rtx, at emit-rtl.c:662 Date: Mon, 17 Mar 2003 16:34:38 +0100 Robert Schiele <rschiele@uni-mannheim.de> writes: |> On Mon, Mar 17, 2003 at 09:29:37AM -0500, Daniel Jacobowitz wrote: |> > If you have a copy of the standard, it's 6.5.6#8. Once a pointer is |> > adjusted to point outside of the original object it must not be |> > dereferenced. Accessing memory in this way produces undefined |> > behavior. |> |> Ok thanks, found it there. |> |> How about this: |> |> void a() { |> double b; |> int c[2]; |> *((int*)&b) && (c[1] = 0); |> } |> |> Exactly same problem. And this time there is no pointer outside well |> defined data area. You agree that this sample is legal code? Ignoring the missing initialisation of b this is undefined under the aliasing rules. Andreas. -- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
next reply other threads:[~2003-03-17 15:36 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-17 15:36 Andreas Schwab [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-24 4:23 rth 2003-03-18 20:29 ebotcazou 2003-03-17 17:16 Robert Schiele 2003-03-17 17:06 Falk Hueffner 2003-03-17 16:56 Joseph S. Myers 2003-03-17 16:26 Robert Schiele 2003-03-17 15:56 Robert Schiele 2003-03-17 15:26 Robert Schiele 2003-03-17 15:26 Falk Hueffner 2003-03-17 14:36 Daniel Jacobowitz 2003-03-17 9:26 Robert Schiele 2003-03-17 9:16 Richard Henderson 2003-03-17 5:16 Robert Schiele 2003-03-16 23:27 rth 2003-03-16 23:26 rth
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=20030317153601.8995.qmail@sources.redhat.com \ --to=schwab@suse.de \ --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: linkBe 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).