From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Xtensa toolchain issue ?
Date: Fri, 4 Jan 2019 10:27:35 +0100 [thread overview]
Message-ID: <20190104102735.52e7e733@windsurf> (raw)
In-Reply-To: <CAMo8BfJR7vgLDONmKDX3S8RLyJBMYmXEKjjEr3JK5JOTHrd5hg@mail.gmail.com>
Hello Max,
As usual, thanks a lot for your feedback, very useful.
On Thu, 3 Jan 2019 14:17:51 -0800, Max Filippov wrote:
> My understanding is that this is not something that could be fixed
> in a generic way, but requires support from the compiler backend.
> Specifically it needs a way to tail-call a variadic function from a
> thunk,
This is intricate compiler stuff. If you have a bit of time to give a
few more details about this, I'd be interested. Of course, that's just
to satisfy my endless curiosity, so if you don't have time/interest,
you can skip this request :-)
> something that is not trivial to do on xtensa architecture.
> The corresponding test in the gcc test suite
> (gcc/testsuite/g++.old-deja/g++.jason/thunk3.C)
> has been disabled since 2002.
>
> The test in the bug that you've referenced still fails on xtensa with
> gcc 8 and gcc 9.
>
> I'll try to implement required support in the xtensa backend for the
> above to work.
Since the issue also happens on OpenRISC, perhaps we need to have some
BR2_TOOLCHAIN_SUPPORTS_XYZ boolean that says whether the gcc version
supports this specific stuff. However, since I don't clearly understand
what the issue is, I wouldn't be able to find a good name for that
BR2_TOOLCHAIN_SUPPORTS_XYZ option.
BR2_TOOLCHAIN_SUPPORTS_TAIL_CALL_VARIADIC_FUNC_FROM_THUNK ? :-)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-04 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:21 [Buildroot] Xtensa toolchain issue ? Thomas Petazzoni
2019-01-03 22:17 ` Max Filippov
2019-01-04 9:27 ` Thomas Petazzoni [this message]
2019-01-04 23:44 ` Max Filippov
2019-01-10 14:56 ` Thomas Petazzoni
2019-01-14 20:09 ` Max Filippov
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=20190104102735.52e7e733@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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