public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99905] [8/9/10/11 Regression] wrong code with -mno-mmx -mno-sse
Date: Tue, 06 Apr 2021 06:53:59 +0000 [thread overview]
Message-ID: <bug-99905-4-yyaX4tNpAX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99905-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99905
Zdenek Sojka <zsojka at seznam dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|wrong code with |[8/9/10/11 Regression]
|-mgeneral-regs-only |wrong code with -mno-mmx
| |-mno-sse
--- Comment #3 from Zdenek Sojka <zsojka at seznam dot cz> ---
(In reply to Zdenek Sojka from comment #2)
> (In reply to Martin Liška from comment #1)
> > > Probably present since -mgeneral-regs-only introduction.
> >
> > Confirmed that, it's since r7-928-gce3a16ff1f59e6db.
>
> Thank you for the bisection.
> If -mgeneral-regs-only is not used, the flag can be replaced by -mno-mmx
> -mno-sse:
>
> $ x86_64-pc-linux-gnu-gcc -Os -mno-mmx -mno-sse testcase.c
> $ ./a.out
> Aborted
... which seems a regression from gcc-6.5.0
next prev parent reply other threads:[~2021-04-06 6:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-04 8:21 [Bug target/99905] New: wrong code with -mgeneral-regs-only zsojka at seznam dot cz
2021-04-06 6:24 ` [Bug target/99905] " marxin at gcc dot gnu.org
2021-04-06 6:51 ` zsojka at seznam dot cz
2021-04-06 6:53 ` zsojka at seznam dot cz [this message]
2021-04-06 7:07 ` [Bug target/99905] [8/9/10/11 Regression] wrong code with -mno-mmx -mno-sse since r7-4540-gb229ab2a712ccd44 marxin at gcc dot gnu.org
2021-04-06 8:00 ` rguenth at gcc dot gnu.org
2021-04-06 17:25 ` jakub at gcc dot gnu.org
2021-04-07 8:48 ` jakub at gcc dot gnu.org
2021-04-07 9:39 ` jakub at gcc dot gnu.org
2021-04-07 9:54 ` [Bug rtl-optimization/99905] " jakub at gcc dot gnu.org
2021-04-12 23:02 ` cvs-commit at gcc dot gnu.org
2021-04-12 23:03 ` [Bug rtl-optimization/99905] [8/9/10 " jakub at gcc dot gnu.org
2021-04-20 9:46 ` cvs-commit at gcc dot gnu.org
2021-04-20 9:52 ` [Bug rtl-optimization/99905] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:52 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` jakub at gcc dot gnu.org
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=bug-99905-4-yyaX4tNpAX@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).