FX Coudert via Gcc writes:
> Hi,
>
> I am trying to reduce the number of unneeded fixincludes that are used
> on darwin (because fixincluded headers make it impossible to change
> SDK once the compiler is built, which is common practice in the macOS
> world, and quite useful).
It's the same prob
Snapshot gcc-11-20240605 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20240605/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
> Am 05.06.2024 um 16:08 schrieb Michael Matz :
>
> Hey,
>
>> On Wed, 5 Jun 2024, David Brown wrote:
>>
>> The ideal here would be to have some way to tell gcc that a given
>> function has the semantics of a different function. For example, a
>> programmer might have several implementations
Hey,
On Wed, 5 Jun 2024, David Brown wrote:
> The ideal here would be to have some way to tell gcc that a given
> function has the semantics of a different function. For example, a
> programmer might have several implementations of "memcpy" that are
> optimised for different purposes based on
Hello,
On Tue, 4 Jun 2024, Jakub Jelinek wrote:
> On Tue, Jun 04, 2024 at 07:43:40PM +0200, Michael Matz via Gcc wrote:
> > (Well, and without reverse-recognition of isfinite-like idioms in the
> > sources. That's orthogonal as well.)
>
> Why? If isfinite is better done by a libcall, why isn'
On 04/06/2024 19:43, Michael Matz via Gcc wrote:
Hello,
On Tue, 4 Jun 2024, Richard Biener wrote:
A pragmatic solution might be a new target hook, indicating a specified
builtin is not to be folded into an open-coded form.
Well, that's what the mechanism behind -fno-builtin-foobar is suppose
On 6/4/24 8:51 PM, Erick Kuo-Chen Huang(黃國鎭) via Gcc-help wrote:
Hi,
We would like to know which GCC version start to support RISC-V RVV1.0 ?
We appreciate for your help.
gcc-14.
Jeff
