From: StrawberryTea <look@strawberrytea.xyz>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: 69689@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
Andrea Corallo <acorallo@gnu.org>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#69689: 30.0.50; cannot native compile with -flto in native-comp-compiler-options
Date: Sun, 17 Mar 2024 17:12:09 -0500 [thread overview]
Message-ID: <877ci0v77q.fsf@strawberrytea.xyz> (raw)
In-Reply-To: <87zfuwy0gq.fsf@> ("Björn Bidar"'s message of "Mon, 18 Mar 2024 00:09:41 +0200")
Björn Bidar <bjorn.bidar@thaodan.de> writes:
> StrawberryTea <look@strawberrytea.xyz> writes:
>
>>>
>>> Andrea
>>
>> I see. I am going to report this to the GCC bug tracker to try and get
>> it fixed. I would like to use LTO with native compilation, even if it
>> would not bring any measurable advantages. And I feel there has to be
>> some GCC person that knows how to fix this.
>
> Did you read my mail? I am able to compile elisp files with -flto in
> native-comp-compiler-options.
>
> The errors must be somewhere on your side.
Oh, I see. I did not read your mail. I am sorry for that. Thank you for
the information. I will add this to the Gentoo bug report.
next prev parent reply other threads:[~2024-03-17 22:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 3:19 bug#69689: 30.0.50; cannot native compile with -flto in native-comp-compiler-options StrawberryTea
2024-03-10 6:24 ` Eli Zaretskii
2024-03-10 17:32 ` StrawberryTea
2024-03-10 17:47 ` Eli Zaretskii
2024-03-10 21:08 ` Paul Eggert
2024-03-11 13:38 ` Eli Zaretskii
2024-03-12 1:03 ` Paul Eggert
2024-03-15 17:02 ` Andrea Corallo
2024-03-17 18:17 ` StrawberryTea
2024-03-17 22:09 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87zfuwy0gq.fsf@>
2024-03-17 22:12 ` StrawberryTea [this message]
2024-04-02 8:56 ` Andrea Corallo
2024-03-12 4:23 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=877ci0v77q.fsf@strawberrytea.xyz \
--to=look@strawberrytea.xyz \
--cc=69689@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=bjorn.bidar@thaodan.de \
--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).