From: Jeff Law <law@redhat.com>
To: "Martin Liška" <mliska@suse.cz>,
"Wilco Dijkstra" <Wilco.Dijkstra@arm.com>,
"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR85678: Change default to -fno-common
Date: Thu, 05 Dec 2019 15:40:00 -0000 [thread overview]
Message-ID: <bd769254-2c0a-0956-5d87-a1687087caa1@redhat.com> (raw)
In-Reply-To: <beac31e2-416e-ed62-d7ed-41070c35e093@suse.cz>
On 12/5/19 2:16 AM, Martin Liška wrote:
>
>>
>> Of the ~450 packages affected I'd estimate that even with the opt-out
>> mechanism we're still going to have to fix ~100 packages immediately
>> because they don't honor the flags injection mechanisms which the
>> opt-out approach relies upon.
>
> Fortunately, we switch at openSUSE to use -fpie by default and our packages
> honor the flags ;)
:-) Fedora is in much worse shape than RHEL simply because we haven't
pushed hard on the injection issues for Fedora and because there's a ton
of stuff in Fedora that isn't in RHEL.
So it looks like ~150 packages in Fedora that are affected by the
-fno-common change and which aren't honoring the flags injection. Not
great, but probably manageable.
>
> I would like to mention here that key work is to report and explain that
> to upstream. Only that will help for the future to reduce number of
> packages
> that will need the -fcommon option. That's the biggest effort in my
> opinion.
Absolutely. I've found this takes more time than fixing the issue in
the first place on other stuff and I'd expect it to be no different than
the -fno-common stuff.
jeff
next prev parent reply other threads:[~2019-12-05 15:40 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 16:00 Wilco Dijkstra
2019-10-25 19:11 ` Georg-Johann Lay
2019-10-26 12:45 ` Iain Sandoe
2019-10-26 13:27 ` Segher Boessenkool
2019-10-25 22:44 ` Segher Boessenkool
2019-10-26 18:21 ` Jeff Law
2019-10-28 16:15 ` Wilco Dijkstra
2019-10-28 18:44 ` Segher Boessenkool
2019-10-27 5:58 ` Harald van Dijk
2019-10-29 13:06 ` [PATCH v2] " Wilco Dijkstra
2019-10-30 14:10 ` Richard Biener
2019-10-30 14:33 ` Wilco Dijkstra
2019-11-04 13:39 ` Richard Biener
2019-11-04 14:39 ` Wilco Dijkstra
2019-11-05 12:25 ` Richard Biener
2019-11-05 17:17 ` [PATCH v3] " Wilco Dijkstra
2019-11-17 23:35 ` Jeff Law
2019-11-21 0:41 ` [PATCH] Fix libgo build (was Re: [PATCH v3] PR85678: Change default to -fno-common) Jakub Jelinek
2019-11-21 0:46 ` Rainer Orth
2019-11-21 1:04 ` Jakub Jelinek
2019-11-21 11:40 ` Rainer Orth
2019-11-21 11:40 ` Jakub Jelinek
2019-11-21 11:54 ` Wilco Dijkstra
2019-11-21 11:58 ` Jakub Jelinek
2019-11-21 1:11 ` Ian Lance Taylor
2019-11-29 13:17 ` [PATCH] PR85678: Change default to -fno-common Martin Liška
2019-11-29 14:46 ` Wilco Dijkstra
2019-11-29 15:09 ` Martin Liška
2019-12-01 4:17 ` Jeff Law
2019-12-04 15:26 ` Wilco Dijkstra
2019-12-04 17:27 ` Jeff Law
2019-12-04 21:03 ` Joseph Myers
2019-12-04 21:14 ` Jeff Law
2019-12-05 9:16 ` Martin Liška
2019-12-05 10:01 ` Tobias Burnus
2019-12-05 13:18 ` Wilco Dijkstra
2019-12-05 16:49 ` Jeff Law
2019-12-05 15:40 ` Jeff Law [this message]
2019-10-28 19:04 David Edelsohn
2019-10-28 19:46 ` Richard Biener
2019-10-28 20:06 ` Jeff Law
2019-10-28 20:29 ` Wilco Dijkstra
2019-10-28 21:52 ` Iain Sandoe
2019-10-29 8:42 ` Richard Biener
2019-10-29 12:15 ` Wilco Dijkstra
2019-10-29 12:27 ` Iain Sandoe
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=bd769254-2c0a-0956-5d87-a1687087caa1@redhat.com \
--to=law@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@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).