public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fredrik.hederstierna@securitas-direct.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/100491] Code generation get worse when including function prototype on ARM
Date: Sun, 09 May 2021 10:45:22 +0000	[thread overview]
Message-ID: <bug-100491-4-0bTn1wYFm6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100491-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100491

--- Comment #1 from Fredrik Hederstierna <fredrik.hederstierna@securitas-direct.com> ---
Created attachment 50780
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50780&action=edit
makefile

Adding makefile to compile test example. See in makefile how to
trigger/untrigger the unexpected condition.

  reply	other threads:[~2021-05-09 10:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09 10:43 [Bug c/100491] New: " fredrik.hederstierna@securitas-direct.com
2021-05-09 10:45 ` fredrik.hederstierna@securitas-direct.com [this message]
2021-05-09 17:22 ` [Bug ipa/100491] [11 Regression] IPA-SRA is not happening any more pinskia at gcc dot gnu.org
2021-05-10  6:45 ` fredrik.hederstierna@securitas-direct.com
2021-05-10  7:30 ` fredrik.hederstierna@securitas-direct.com
2021-05-10  7:31 ` fredrik.hederstierna@securitas-direct.com
2021-05-10  8:09 ` [Bug ipa/100491] [11/12 " rguenth at gcc dot gnu.org
2021-05-12 13:31 ` jamborm at gcc dot gnu.org
2021-07-28  7:06 ` rguenth at gcc dot gnu.org
2022-01-03 17:47 ` jamborm at gcc dot gnu.org
2022-01-20 13:55 ` [Bug ipa/100491] [11 " rguenth at gcc dot gnu.org
2022-01-24  7:08 ` fredrik.hederstierna@securitas-direct.com
2022-04-21  7:49 ` rguenth at gcc dot gnu.org
2023-05-29 10:04 ` 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-100491-4-0bTn1wYFm6@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).