public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111500] [arm-none-eabi-gcc] / suboptimal optimization / subs followed by cmp (et alii)
Date: Mon, 25 Sep 2023 06:52:49 +0000 [thread overview]
Message-ID: <bug-111500-4-v0E9WY91r1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111500-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111500
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Luke from comment #4)
> the a.i file for example #1a is:
> # 1 "a.c"
> # 1 "/tmp//"
> # 1 "<built-in>"
> # 1 "<command-line>"
> # 1 "a.c"
> void artiSUBS() {
> for (int i=100; i>0; i--)
> *(volatile int*)0xE000E014 = i;
> }
>
> the command-line was:
> > arm-none-eabi-gcc -save-temps -S a.c -O3 -g -mcpu=cortex-m0plus -mthumb -Wall --specs=nosys.specs -nostdlib -fdata-sections -ffunction-sections -ffreestanding -Winline
>
> and the resulting a.s file contains that subs/cmp sequence...
This is most likely a dup of bug 104773.
next prev parent reply other threads:[~2023-09-25 6:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 14:55 [Bug c/111500] New: [arm-none-eabi-gcc] / suboptimal optimization gnu.arne at wgboome dot org
2023-09-20 16:16 ` [Bug target/111500] " pinskia at gcc dot gnu.org
2023-09-20 19:14 ` gnu.arne at wgboome dot org
2023-09-25 4:46 ` cptarse-luke at yahoo dot com
2023-09-25 4:52 ` cptarse-luke at yahoo dot com
2023-09-25 6:43 ` [Bug target/111500] [arm-none-eabi-gcc] / suboptimal optimization / subs followed by cmp (et alii) pinskia at gcc dot gnu.org
2023-09-25 6:48 ` pinskia at gcc dot gnu.org
2023-09-25 6:52 ` pinskia at gcc dot gnu.org [this message]
2023-09-25 6:53 ` pinskia at gcc dot gnu.org
2023-09-25 7:09 ` cptarse-luke at yahoo dot com
2023-09-25 7:28 ` cptarse-luke at yahoo dot com
2023-09-25 10:45 ` cptarse-luke at yahoo dot com
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-111500-4-v0E9WY91r1@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).