[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#24720: Performance impact of -no-pie
From: |
Eli Zaretskii |
Subject: |
bug#24720: Performance impact of -no-pie |
Date: |
Thu, 20 Oct 2016 10:04:35 +0300 |
> From: Alex <agrambot@gmail.com>
> Cc: rgm@gnu.org, eggert@cs.ucla.edu, 24720@debbugs.gnu.org
> Date: Wed, 19 Oct 2016 13:45:47 -0600
>
> > The default switches are known, so they don't need to be spelled out
> > in the report. It's the non-default ones that needs to be shown.
>
> I agree that they don't need to be in the report, but just having them
> in a variable (e.g. system-configuration-options) would make it easier
> for users to see what the default switches are.
>
> For example, I would have compared system-configuration-options between
> the slow and fast builds and noticed that the fast build had '-O2' while
> the slow one didn't, and this report wouldn't have been filed.
You have that information in config.log, so I'm unsure why you
couldn't find it if you looked for it.
- bug#24720: Performance impact of -no-pie, Paul Eggert, 2016/10/17
- Message not available
- bug#24720: Performance impact of -no-pie, Paul Eggert, 2016/10/17
- bug#24720: Performance impact of -no-pie, Alex, 2016/10/18
- bug#24720: Performance impact of -no-pie, Glenn Morris, 2016/10/18
- bug#24720: Performance impact of -no-pie, Paul Eggert, 2016/10/18
- bug#24720: Performance impact of -no-pie, Alex, 2016/10/19
- bug#24720: Performance impact of -no-pie, Eli Zaretskii, 2016/10/19
- bug#24720: Performance impact of -no-pie, Alex, 2016/10/19
- bug#24720: Performance impact of -no-pie,
Eli Zaretskii <=
- bug#24720: Performance impact of -no-pie, Alex, 2016/10/20
- bug#24720: Performance impact of -no-pie, Alex, 2016/10/26
bug#24720: Performance impact of -no-pie, Cesar Quiroz, 2016/10/18