public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: roger@eyesopen.com
To: gcc-gnats@gcc.gnu.org
Cc: jh@suse.cz
Subject: target/6456: builtin memset broken on x86 with -minline-all-stringops
Date: Thu, 25 Apr 2002 12:16:00 -0000	[thread overview]
Message-ID: <20020425190653.22269.qmail@sources.redhat.com> (raw)


>Number:         6456
>Category:       target
>Synopsis:       builtin memset broken on x86 with -minline-all-stringops
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          wrong-code
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 25 12:16:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Roger Sayle <roger@eyesopen.com>
>Release:        mainline CVS 20020425 (probably also 3.1 prerelease)
>Organization:
>Environment:
i686-pc-linux-gnu (RedHat 7.2)
>Description:
The x86 backend is currently generates incorrect code for
builtin memset, when using "-minline-all-stringops".  This
is specific to the ia-32 backend.  Interestingly, GCC uses
different code sequences for "-march=athlon" which doesn't
exhibit the problem.
>How-To-Repeat:
The problem can be reproduced by compiling and running the
memset correctness test, gcc.c-torture/execute/memset-1.c,
with command line options "-O2 -minline-all-stringops".

Once I get a PR number, I'll submit a new gcc.dg testcase
to gcc-patches to check for this problem on i?86-*-*.
>Fix:
For the time being, don't specify "-minline-all-stringops".
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-25 19:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25 12:16 roger [this message]
2002-05-03 19:14 sayle

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=20020425190653.22269.qmail@sources.redhat.com \
    --to=roger@eyesopen.com \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=jh@suse.cz \
    /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).