all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: 65988-done@debbugs.gnu.org
Subject: bug#65988: 30.0.50; Emacs and -O3 compiler optimization
Date: Fri, 15 Sep 2023 14:29:38 +0300	[thread overview]
Message-ID: <83o7i3k731.fsf@gnu.org> (raw)
In-Reply-To: <86bke36bab.fsf@gnu.org> (message from Arash Esbati on Fri, 15 Sep 2023 11:22:36 +0200)

> From: Arash Esbati <arash@gnu.org>
> Date: Fri, 15 Sep 2023 11:22:36 +0200
> 
> Presuming that the note above applies to GCC on all platforms, I suggest
> to change/adjust the following example in INSTALL[2]:
> 
>   Here's an example of a 'configure' invocation, assuming a Bourne-like
>   shell such as Bash, which uses these variables:
> 
>     ./configure \
>       CPPFLAGS='-I/foo/myinclude' LDFLAGS='-L/bar/mylib' \
>       CFLAGS='-O3' LIBS='-lfoo -lbar'
> 
>   (this is all one shell command).  This tells 'configure' to instruct the
>   preprocessor to look in the '/foo/myinclude' directory for header
>   files (in addition to the standard directories), instruct the linker
>   to look in '/bar/mylib' for libraries, pass the -O3 optimization
>   switch to the compiler, and link against libfoo and libbar
>   libraries in addition to the standard ones.
> 
> IIRC this was the place where I picked up the -O3 switch for the script
> I wrote for building Emacs.

You really shouldn't treat what's in INSTALL so literally: it's just
an example to illustrate how to use these switches.

I changed it not to use -O3.





      reply	other threads:[~2023-09-15 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  9:22 bug#65988: 30.0.50; Emacs and -O3 compiler optimization Arash Esbati
2023-09-15 11:29 ` Eli Zaretskii [this message]

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=83o7i3k731.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65988-done@debbugs.gnu.org \
    --cc=arash@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.