public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: glen@imodulo.com
To: gcc-gnats@gcc.gnu.org
Subject: optimization/6909: problem w/ -Os on modified loop-2c.c test case.
Date: Sun, 02 Jun 2002 13:36:00 -0000	[thread overview]
Message-ID: <20020602203041.18544.qmail@sources.redhat.com> (raw)


>Number:         6909
>Category:       optimization
>Synopsis:       problem w/ -Os on modified loop-2c.c test case.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jun 02 13:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Glen Nakamura
>Release:        3.1.1 20020526 (prerelease), 3.2? (experimental)
>Organization:
>Environment:
i586-pc-linux-gnu
>Description:
Modified gcc.c-torture/execute/loop-2c.c test case fails on i586-pc-linux-gnu when compiling w/ -Os.  I actually noticed this problem on the 3.1 branch, but I think the mainline is also affected...  I'll verify this and post a patch.
>How-To-Repeat:
gcc -Os loop-2c-new.c
./a.out
>Fix:
patch pending...
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="loop-2c-new.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="loop-2c-new.c"

aW50IGFbMl07CgpfX2lubGluZV9fIGYgKGIsIG8pCnsKICB1bnNpZ25lZCBpbnQgaTsKICBpbnQg
KnA7CiAgZm9yIChwID0gJmFbYl0sIGkgPSBiOyAtLWkgPD0gKH4wIC0gMSk7ICkKICAgICotLXAg
PSBpICogMyArIG87Cn0KCmcoaW50IGIpCnsKICBmIChiLCAoaW50KWEpOwp9CgptYWluICgpCnsK
ICBhWzBdID0gYVsxXSA9IDA7CiAgZyAoMik7CiAgaWYgKGFbMF0gIT0gKGludClhIHx8IGFbMV0g
IT0gKGludClhICsgMykKICAgIGFib3J0ICgpOwogIGV4aXQgKDApOwp9Cg==


             reply	other threads:[~2002-06-02 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02 13:36 glen [this message]
2002-06-02 18:56 Glen Nakamura

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=20020602203041.18544.qmail@sources.redhat.com \
    --to=glen@imodulo.com \
    --cc=gcc-gnats@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).