public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: gcc@gcc.gnu.org
Subject: Re: How to avoid some built-in expansions in gcc?
Date: Fri, 31 May 2024 14:56:40 +0100	[thread overview]
Message-ID: <CAH6eHdTxcz2Bx1watRPfRKZCzVHpU0vGF9bU5Mp9sZ83Uc0QvQ@mail.gmail.com> (raw)
In-Reply-To: <c09ef172-34e3-4843-b5cf-28d4c4184f91@gjlay.de>

On Fri, 31 May 2024 at 14:52, Georg-Johann Lay <avr@gjlay.de> wrote:
>
> What's the recommended way to stop built-in expansions in gcc?
>
> For example, avr-gcc expands isinff() to a bloated version of an
> isinff() implementation that's written in asm (PR115307).

Did you try -fno-builtin-isinff ?

  reply	other threads:[~2024-05-31 13:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 13:52 Georg-Johann Lay
2024-05-31 13:56 ` Jonathan Wakely [this message]
2024-05-31 14:53   ` Georg-Johann Lay
2024-05-31 14:53     ` Jonathan Wakely
2024-05-31 15:00 ` Paul Koning
2024-05-31 15:06   ` Georg-Johann Lay
2024-05-31 15:23     ` Paul Koning
2024-05-31 17:32       ` Richard Biener
2024-05-31 18:56         ` Georg-Johann Lay
2024-05-31 20:12           ` Richard Biener
2024-06-01 15:41             ` Georg-Johann Lay
2024-06-01 17:30               ` Richard Biener
2024-06-04 14:55                 ` Michael Matz
2024-06-04 16:43                   ` Richard Biener
2024-06-04 17:43                     ` Michael Matz
2024-06-04 17:48                       ` Jakub Jelinek
2024-06-05 13:52                         ` Michael Matz
2024-06-05 13:33                       ` David Brown
2024-06-05 14:08                         ` Michael Matz
2024-06-05 14:16                           ` Richard Biener

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=CAH6eHdTxcz2Bx1watRPfRKZCzVHpU0vGF9bU5Mp9sZ83Uc0QvQ@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=avr@gjlay.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).