public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114532] gcc -fno-common option causes performance degradation on certain architectures
Date: Wed, 05 Jun 2024 09:29:35 +0000	[thread overview]
Message-ID: <bug-114532-4-XCCFp0iHn4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114532-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Anyway if you really require a specific order of some data you need to either
use -fno-toplevel-reorder, or group the data with a struct or linker script
explicitly.

Relying on any implicit behavior like -fcommon is just fragile and it may
"break" if the compiler or the linker are changed.

  parent reply	other threads:[~2024-06-05  9:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30  9:47 [Bug c/114532] New: " h13958451065 at 163 dot com
2024-03-30 18:48 ` [Bug middle-end/114532] " pinskia at gcc dot gnu.org
2024-06-04  1:38 ` zhaohaifeng4 at huawei dot com
2024-06-04  1:41 ` sjames at gcc dot gnu.org
2024-06-04 11:19 ` david at westcontrol dot com
2024-06-05  4:12 ` zhaohaifeng4 at huawei dot com
2024-06-05  5:46 ` xry111 at gcc dot gnu.org
2024-06-05  8:24 ` david at westcontrol dot com
2024-06-05  8:46 ` zhaohaifeng4 at huawei dot com
2024-06-05  9:26 ` xry111 at gcc dot gnu.org
2024-06-05  9:29 ` xry111 at gcc dot gnu.org [this message]
2024-06-05  9:30 ` david at westcontrol 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-114532-4-XCCFp0iHn4@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).