unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 24720@debbugs.gnu.org
Subject: bug#24720: Performance impact of -no-pie
Date: Tue, 25 Oct 2016 22:30:31 -0600	[thread overview]
Message-ID: <87twbz7mvs.fsf@gmail.com> (raw)
In-Reply-To: <87lgxi8y8r.fsf@gmail.com> (Alex's message of "Thu, 20 Oct 2016 16:13:56 -0600")

Alex <agrambot@gmail.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> 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.
>
> Yes, in this case I could have looked in there, but that file is
> overwritten with every ./configure, right? That means there's no
> guarantee that what's listed there is for a given Emacs build.
>
> I think that configuration options should be tied to, and viewable
> through, Emacs regardless of the value it's set to. If report-emacs-bugs
> needs to know when to hide the options, then perhaps a new variable
> could be introduced for that purpose.

For example, in configure.ac, if the block that calculates
emacs_config_options was moved to the bottom before

AC_DEFINE_UNQUOTED(EMACS_CONFIG_OPTIONS, "${emacs_config_options}",
		   [Define to the options passed to configure.])

then system-configuration-options is:

"dummy pkg-config 'CFLAGS=-g3 -O2' 'CPPFLAGS=  ' 'LDFLAGS= '"

I'm not sure what 'dummy pkg-config' is doing there, but otherwise I
think that it would be nice to have this as the default.





  reply	other threads:[~2016-10-26  4:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 20:18 bug#24720: Performance impact of -no-pie Paul Eggert
     [not found] ` <handler.24720.B.147673554717923.ack@debbugs.gnu.org>
2016-10-17 20:26   ` Paul Eggert
2016-10-18  4:06     ` Alex
2016-10-18 15:59       ` Glenn Morris
2016-10-18 16:21         ` Paul Eggert
2016-10-19  4:41         ` Alex
2016-10-19  7:04           ` Eli Zaretskii
2016-10-19 19:45             ` Alex
2016-10-20  7:04               ` Eli Zaretskii
2016-10-20 22:13                 ` Alex
2016-10-26  4:30                   ` Alex [this message]
2016-10-18  5:54 ` Cesar Quiroz

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87twbz7mvs.fsf@gmail.com \
    --to=agrambot@gmail.com \
    --cc=24720@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).