public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Richard Earnshaw via Gcc-help <gcc-help@gcc.gnu.org>
Cc: David Brown <david@westcontrol.com>,
	 Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Subject: Re: pragma GCC optimize prevents inlining
Date: Tue, 09 Jan 2024 14:38:27 +0100	[thread overview]
Message-ID: <87frz61vak.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <ea1fe6f1-7b08-488a-afed-f479feb5b989@foss.arm.com> (Richard Earnshaw via Gcc-help's message of "Thu, 4 Jan 2024 16:37:09 +0000")

* Richard Earnshaw via Gcc-help:

> The general problem here is that the AST does not carry enough
> information to handle all these cases within a single function.  To
> merge wrap/no-wrap code, for example, we'd need separate codes for
> ADD, SUBTRACT, MULTIPLY, etc.

__builtin_add_overflow et al. are already specified to implement
wraparound behavior on overflow, so that particular case should be
covered to some extent.

Thanks,
Florian


  reply	other threads:[~2024-01-09 13:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  9:01 Hashan Gayasri
2024-01-04  9:27 ` LIU Hao
2024-01-05  0:56   ` Hashan Gayasri
2024-01-04 14:51 ` David Brown
2024-01-04 15:03   ` Segher Boessenkool
2024-01-04 15:24     ` David Brown
2024-01-04 16:37       ` Richard Earnshaw
2024-01-09 13:38         ` Florian Weimer [this message]
2024-01-04 16:55       ` Segher Boessenkool
2024-01-05 14:24         ` David Brown
2024-01-05 15:00           ` Segher Boessenkool
2024-01-05 15:53             ` David Brown
2024-01-05 18:19               ` Segher Boessenkool
2024-01-06 17:02                 ` David Brown
2024-01-07 17:51                   ` Segher Boessenkool
2024-01-07 18:36                     ` Gabriel Ravier
2024-01-08 15:53                     ` David Brown

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=87frz61vak.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=Richard.Earnshaw@foss.arm.com \
    --cc=david@westcontrol.com \
    --cc=gcc-help@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).