public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rassahah@neofonie.de
Subject: Re: optimization/10185: [3.3/3.4 regression] Wrong code with 3-int-structs & optimization
Date: Fri, 21 Mar 2003 15:40:00 -0000	[thread overview]
Message-ID: <20030321154024.5493.qmail@sources.redhat.com> (raw)

Old Synopsis: Wrong code with 3-int-structs & optimization
New Synopsis: [3.3/3.4 regression] Wrong code with 3-int-structs & optimization

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Mar 21 15:40:24 2003
State-Changed-Why:
    Confirmed, a regression on 3.3 and mainline w.r.t. 3.2.2.
    Here's a slightly simpler code:
    --------------------
    typedef struct {
      int x1, dummy1, dummy2;
    } X;
    
    void barrier (int *dummy) {}
    
    main ()
    {
      static X x[] = {{1}, {2}, {5}};
      int i=3, flag=0;
    
      barrier(&i);
      
      while (i--)
        if (x[i].x1 == 2)  // should trigger for i==1
          flag = 1;
      
      if (flag != 1)
        abort ();
    }
    -------------------------------
    The abort() shouldn't be triggered, but is if compiled 
    with -O2 in 3.3 and mainline:
    
    g/x> /home/bangerth/bin/gcc-3.2.2-pre/bin/gcc -O2 x.c ; ./a.out
    g/x> /home/bangerth/bin/gcc-3.3-pre/bin/gcc -O2 x.c ; ./a.out
    Aborted
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/gcc -O2 x.c ; ./a.out
    Aborted
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10185


             reply	other threads:[~2003-03-21 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 15:40 bangerth [this message]
2003-03-21 22:56 Steven Bosscher
2003-03-22  1:16 Janis Johnson
2003-03-22  8:16 Glen Nakamura
2003-03-24 18:39 Jan Hubicka
2003-03-24 19:08 mmitchel

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=20030321154024.5493.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=rassahah@neofonie.de \
    /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).