From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>,
Adhemerval Zanella Netto via Libc-help <libc-help@sourceware.org>
Cc: Abhijit Ray Chaudhury <abhijit.ray.chaudhury@gmail.com>
Subject: Re: compiling glibc using -fasynchronous-unwind-tables for arm
Date: Wed, 15 Mar 2023 16:52:42 -0300 [thread overview]
Message-ID: <7d1b9611-13d1-65f0-9b47-0f7d01cec66c@linaro.org> (raw)
In-Reply-To: <87jzzi14fx.fsf@oldenburg.str.redhat.com>
On 15/03/23 11:20, Florian Weimer wrote:
> * Adhemerval Zanella Netto via Libc-help:
>
>> And I have tested with both:
>>
>> CC="arm-glibc-linux-gnueabihf-gcc -fasynchronous-unwind-tables"
>>
>> and
>>
>> CC=arm-glibc-linux-gnueabihf-gcc CFLAGS="-O2 -fasynchronous-unwind-tables"
>>
>> I also tested with gcc from ubuntu22 to check if this might something
>> I haven't enabled on my toolchain (since I don't build all languages),
>> but again I did not see any issue.
>
> It probably depends on whether libgcc.a has been built with
> optimizations or not.
Indeed this looks like https://sourceware.org/bugzilla/show_bug.cgi?id=29621 .
Does the build work if you manually adds the -fasynchronous-unwind-tables
on config.make?
next prev parent reply other threads:[~2023-03-15 19:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 10:04 Abhijit Ray Chaudhury
2023-03-14 9:18 ` Abhijit Ray Chaudhury
2023-03-14 18:47 ` Adhemerval Zanella Netto
2023-03-15 8:36 ` Abhijit Ray Chaudhury
2023-03-15 12:59 ` Adhemerval Zanella Netto
2023-03-15 14:20 ` Florian Weimer
2023-03-15 19:52 ` Adhemerval Zanella Netto [this message]
2023-03-16 10:59 ` Abhijit Ray Chaudhury
2023-03-17 13:37 ` Abhijit Ray Chaudhury
2023-03-20 17:00 ` Adhemerval Zanella Netto
2023-03-21 11:30 ` Abhijit Ray Chaudhury
2023-03-22 11:56 ` Adhemerval Zanella Netto
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=7d1b9611-13d1-65f0-9b47-0f7d01cec66c@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=abhijit.ray.chaudhury@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-help@sourceware.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.
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).