From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: GCC Development <gcc@gcc.gnu.org>
Subject: Re: gcc_assert() and inhibit_libc
Date: Tue, 17 Aug 2021 10:41:52 +0200 [thread overview]
Message-ID: <90a3deb0-d80f-cdd4-3027-d64aeadc7d3c@embedded-brains.de> (raw)
In-Reply-To: <CADzB+2mGnbrz2e-HEzYLAY-e=kBK5LaNGTxWxReUcQbqtf0Wmg@mail.gmail.com>
On 16/08/2021 18:50, Jason Merrill wrote:
> On Mon, Aug 16, 2021 at 9:51 AM Sebastian Huber
> <sebastian.huber@embedded-brains.de> wrote:
>> On 16/08/2021 14:33, Martin Liška wrote:
>>> On 8/12/21 4:31 PM, Sebastian Huber wrote:
>>>> This would be suitable for me, however, I am not sure if you want such
>>>> a customization feature just for a niche operating system.
>>> I don't see a reason why not.
>>> Please send a patch.
>> Ok, good. I will try to figure out what can be done. One problem is that
>> tsystem.h is included before tm.h. Independent of this Joseph S. Myers
>> said in the recent patch review with respect to the gcov_type size that
>> removing tm.h from the target libraries is a development goal.
>>
>> I guess we have a couple of options.
>>
>> 1. Detect the presence of __assert_func and add the result to tconfig.h.
>> This can't be a link time check, since libgcc is build before Newlib.
>>
>> 2. Use __builtin_trap() instead of abort() if inhibit_libc is defined.
> I still think this seems the most straightforward approach.
I sent a patch for this:
https://gcc.gnu.org/pipermail/gcc-patches/2021-August/577544.html
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2021-08-17 8:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 12:44 Sebastian Huber
2021-07-22 12:15 ` Richard Biener
2021-08-06 17:26 ` Sebastian Huber
2021-08-12 14:31 ` Jason Merrill
2021-08-12 14:08 ` Martin Liška
2021-08-12 14:12 ` Sebastian Huber
2021-08-12 14:29 ` Martin Liška
2021-08-12 14:31 ` Sebastian Huber
2021-08-16 12:33 ` Martin Liška
2021-08-16 13:50 ` Sebastian Huber
2021-08-16 16:50 ` Jason Merrill
2021-08-16 17:06 ` Jakub Jelinek
2021-08-16 18:57 ` Jeff Law
2021-08-17 8:41 ` Sebastian Huber [this message]
2021-08-16 17:05 ` Joseph Myers
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=90a3deb0-d80f-cdd4-3027-d64aeadc7d3c@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc@gcc.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.
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).