> On 17 Mar 2025, at 19:43, Toon Moene wrote:
>
> I was eager to try the new rust updates ...
>
> But I got this:
>
> error[E0554]: `#![feature]` may not be used on the stable release channel
> --> src/lib.rs:19:1
> |
> 19 | #![feature(extern_types)]
> | ^
>
> F
Hi,
The background here is that I made a trial implementation of P1494r4 -
std::observable() - and want to produce testcases.
—— so …..
I am looking for either examples where GCC produces time-travel optimisation
(or alternately some evidence that these are not expected).
(In case someone is
> On 23 Sep 2024, at 15:33, Jonathan Wakely wrote:
>
> On Mon, 23 Sept 2024 at 14:36, enh wrote:
>>
>> it doesn't make the patch _management_ problem better ("now i have two
>> problems"), but https://github.com/landley/toybox takes the "why not both?"
>> approach --- you can use pull reque
> On 3 Sep 2024, at 16:08, Jason Merrill via Gcc wrote:
>
> On 9/3/24 7:30 AM, Jonathan Wakely wrote:
>> On Tue, 3 Sept 2024, 10:15 Iain Sandoe, > <mailto:i...@sandoe.co.uk>> wrote:
>>Hi Folks,
>>When we build a C++ binary module (CMI/BMI), we ob
> On 3 Sep 2024, at 13:59, Nathaniel Shead wrote:
>
> On Tue, Sep 03, 2024 at 10:14:29AM +0100, Iain Sandoe wrote:
>> Hi Folks,
>>
>> When we build a C++ binary module (CMI/BMI), we obviously have access to its
>> source to produce diagnostics, all fine.
>
Hi Folks,
When we build a C++ binary module (CMI/BMI), we obviously have access to its
source to produce diagnostics, all fine.
However, when we consume that module we might also need access to the sources
used to build it - since diagnostics triggered in the consumer can refer back
to the sou
et needed to alter them to work
with the compiler ) - it is not their mission to rewrite headers in some more
generic manner.
>> On Aug 31, 2024, at 11:01 PM, Iain Sandoe wrote:
>> 0. Which macOS architecture you are installing on (Arm64 is not supported by
>> upstream y
Hello Andy,
> On 31 Aug 2024, at 23:14, Andy Miller via Gcc wrote:
> After apparently easily installing GCC 14.2 into macOS 12.7.4,
> directly from https://gcc.gnu.org/gcc-14/
Please identify:
0. Which macOS architecture you are installing on (Arm64 is not supported by
upstream yet, but the
> On 12 Jul 2024, at 13:47, Richard Biener via Gcc wrote:
>
> The first release candidate for GCC 11.5 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/11.5.0-RC-20240712/
>
> and shortly its mirrors. It has been generated from git commit
> r11-11573-g30ffca55041518.
>
> I have
Hi Basile,
> On 28 Jun 2024, at 11:11, Basile Starynkevitch
> wrote:
> Iain Sandoe wrote:
>
>> If I declare a function __attribute__((noipa, optimize (“-O0”))), I was
>> kinda expecting that it would not be optimized at all ..
>>
>> however it does not se
> On 27 Jun 2024, at 20:06, Richard Biener via Gcc wrote:
>> Am 27.06.2024 um 19:43 schrieb Iain Sandoe :
>>> On 27 Jun 2024, at 14:51, Iain Sandoe wrote:
>>>
>>> If I declare a function __attribute__((noipa, optimize (“-O0”))), I was
>>> kind
> On 27 Jun 2024, at 14:51, Iain Sandoe wrote:
>
> If I declare a function __attribute__((noipa, optimize (“-O0”))), I was kinda
> expecting that it would not be optimized at all ..
>
> however it does not seem to prevent functions called by it from being inline
Hello
If I declare a function __attribute__((noipa, optimize (“-O0”))), I was kinda
expecting that it would not be optimized at all ..
however it does not seem to prevent functions called by it from being inlined
into its body ..
am I missing some additional constraint that should be added?
> On 13 Jun 2024, at 09:13, Richard Biener via Gcc wrote:
>
>
> The first release candidate for GCC 12.4 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/12.4.0-RC-20240613/
>
> and shortly its mirrors. It has been generated from git commit
> r12-10557-g6693b1f3929771.
>
> I ha
> On 6 Jun 2024, at 12:41, Sam James via Gcc wrote:
>
> Andi Kleen via Gcc writes:
>
>> FX Coudert via Gcc writes:
>>
>>> 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 compile
> On 14 May 2024, at 17:31, Jakub Jelinek via Gcc wrote:
>
> The first release candidate for GCC 13.3 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/13.3.0-RC-20240514/
> ftp://gcc.gnu.org/pub/gcc/snapshots/13.3.0-RC-20240514/
>
> and shortly its mirrors. It has been generated
> On 13 May 2024, at 19:43, Iain Sandoe wrote:
>
>
>
>> On 13 May 2024, at 18:46, Richard Biener wrote:
>>
>> On Mon, May 13, 2024 at 6:00 PM Iain Sandoe wrote:
>>>
>>>
>>>
>>>> On 13 May 2024, at 16:05, Iain Sando
> On 13 May 2024, at 18:46, Richard Biener wrote:
>
> On Mon, May 13, 2024 at 6:00 PM Iain Sandoe wrote:
>>
>>
>>
>>> On 13 May 2024, at 16:05, Iain Sandoe via Gcc wrote:
>>>> On 30 Aug 2023, at 00:32, Ben Boeckel via Gcc wrote:
>>&g
> On 13 May 2024, at 16:05, Iain Sandoe via Gcc wrote:
>> On 30 Aug 2023, at 00:32, Ben Boeckel via Gcc wrote:
>>
>> On Tue, Aug 29, 2023 at 18:57:37 +0200, Richard Biener wrote:
>>> I suppose for bootstrapping we could disable ISL during stage1 since
>>&
This
> On 30 Aug 2023, at 00:32, Ben Boeckel via Gcc wrote:
>
> On Tue, Aug 29, 2023 at 18:57:37 +0200, Richard Biener wrote:
>> I suppose for bootstrapping we could disable ISL during stage1 since
>> it enables an optional feature only. Other than that GCC only
>> requires a C++11 compiler fo
> On 3 May 2024, at 21:57, Jakub Jelinek via Gcc wrote:
>
> The second release candidate for GCC 14.1 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/14.1.0-RC-20240503/
> ftp://gcc.gnu.org/pub/gcc/snapshots/14.1.0-RC-20240503/
>
> and shortly its mirrors. It has been generated
> On 30 Apr 2024, at 11:33, Jakub Jelinek via Gcc wrote:
>
> The first release candidate for GCC 14.1 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/14.1.0-RC-20240430/
> ftp://gcc.gnu.org/pub/gcc/snapshots/14.1.0-RC-20240430/
>
> and shortly its mirrors. It has been generated
> On 30 Apr 2024, at 08:33, Iain Sandoe wrote:
>
> Hi,
>
>> On 30 Apr 2024, at 00:39, Andrew Pinski via Gcc wrote:
>>
>> On Mon, Apr 29, 2024 at 4:26 PM Lucier, Bradley J via Gcc
>> wrote:
>>>
>>> The question: How to interpr
Hi,
> On 30 Apr 2024, at 00:39, Andrew Pinski via Gcc wrote:
>
> On Mon, Apr 29, 2024 at 4:26 PM Lucier, Bradley J via Gcc
> wrote:
>>
>> The question: How to interpret scheduling info with the compiler listed
>> below.
>>
>> Specifically, a tight loop that was reported to be scheduled in 23
> On 10 Feb 2024, at 11:33, FX Coudert via Gcc wrote:
> I’m seeing the following analyzer test failures on darwin. They were
> introduced in December, when the tests were moved around:
>
> FAIL: c-c++-common/analyzer/fd-glibc-byte-stream-socket.c
> FAIL: c-c++-common/analyzer/fd-manpage-geta
Hi Arthur,
> On 25 Jan 2024, at 15:03, Arthur Cohen wrote:
> On 1/23/24 08:23, Richard Biener wrote:
>> On Mon, Jan 22, 2024 at 7:51 PM Arthur Cohen
>> wrote:
>>>
>>> Hi everyone,
>>>
>>> In order to increase the development speed of Rust features, we are
>>> seeking feedback on reusing some
> On 15 Jan 2024, at 15:35, Florian Weimer wrote:
>
> * Carlos O'Donell:
>
>> I agree. TLS should be seen more like .bss/.data rather than something
>> that is allocated with malloc().
>
> There wasn't consensus regarding this in 2014. See below.
>
>> If we leak memory via TLS that is a gl
> On 13 Jan 2024, at 07:45, Hanke Zhang via Gcc wrote:
>
> Hi, I'm attempting to compress the size of a field in a structure for
> memory-friendly purposes. I created an IPA pass to achieve this, but I
> ran into some issues as follows:
>
> // original
> struct Foo {
> long a1;
> int a2;
>
Hi Richard,
> On 19 Oct 2023, at 22:49, Richard Sandiford wrote:
> Iain Sandoe writes:
>> I am being bitten by a problem that falls out from the code that emits
>>
>> .arch Armv8.n-a+crc
>>
>> when the arch is less than Armv8-r.
>> The code tha
correction ...
> On 19 Oct 2023, at 17:41, Iain Sandoe wrote:
>
> Hi Richard,
>
>
> I am being bitten by a problem that falls out from the code that emits
>
> .arch Armv8.n-a+crc
>
> when the arch is less than Armv8-r.
> The code that does this, in g
Hi Richard,
I am being bitten by a problem that falls out from the code that emits
.arch Armv8.n-a+crc
when the arch is less than Armv8-r.
The code that does this, in gcc/common/config/aarch64 is quite recent
(2022-09).
--
(I admit the permutations are complex and I might have m
Hi Ryan,
It’s always a good idea to send questions to the mailing list (that gives other
people a chance to answer this - probably better than me).
> On 15 Oct 2023, at 13:40, R jd <3246251196r...@gmail.com> wrote:
> my name is Ryan. I am part of a team that ensures that GCC is ported fo
Hi François,
> On 11 Oct 2023, at 05:49, François Dumont wrote:
> On 08/10/2023 15:59, Iain Sandoe wrote:
>>> On 23 Sep 2023, at 21:10, François Dumont wrote:
>>>
>>> I'm eventually fixing those tests the same way we manage this problem in
>>>
Hi François,
> On 23 Sep 2023, at 21:10, François Dumont wrote:
>
> I'm eventually fixing those tests the same way we manage this problem in
> libstdc++ testsuite.
>
>testsuite: Add optional libstdc++ version namespace in expected diagnostic
>
> When libstdc++ is build with --enable-s
> On 12 Sep 2023, at 20:42, Rainer Orth wrote:
>
> ASSI writes:
>
>> Richard Biener via Gcc writes:
>>> I think we should fix this build problems. Is there a bugzilla with
>>> more details about the problem?
>>
>> No, I don't have an account on that bugtracker.
>>
>> It is possible that t
Hi Richard,
> On 6 Sep 2023, at 13:43, Richard Sandiford via Gcc wrote:
>
> Iain Sandoe writes:
>> On the Darwin aarch64 port, we have a number of cleanup test fails (pretty
>> much corresponding to the [still open]
>> https://gcc.gnu.org/bugzilla/show_bug.cgi
Hi Folks,
On the Darwin aarch64 port, we have a number of cleanup test fails (pretty much
corresponding to the [still open]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39244). However, let’s assume
that bug could be a red herring..
the underlying reason is missing CFI for the set of the FP w
> On 24 May 2023, at 14:09, Paul Koning via Gcc wrote:
>
>
>
>> On May 23, 2023, at 10:08 PM, LIU Hao via Gcc wrote:
>>
>> 在 2023/5/19 20:59, Florian Weimer via Gcc 写道:
>>> * Jonathan Wakely via Gcc:
Unfortunately even the Gmail web UI doesn't offer an unsubscribe
option, despite
Hi Shengyu,
> On 27 Feb 2023, at 13:35, Shengyu Huang via Gcc wrote:
>
> By the way, is it expected that I need to configure with
> `--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk`?
Yes.
- for some time now macOS no longer installs headers in /usr/include (and on
newer
Hi Shengyu
> On 27 Feb 2023, at 13:35, Shengyu Huang via Gcc wrote:
> Sorry for the late reply. I just built gcc-12-2 on my machine with bootstrap
> and it worked.
great,
>
> However, maybe due to some missing configuration, building without bootstrap
> does not work on my machine (developme
Hi Shengyu,
oops finger-trouble…
> On 22 Feb 2023, at 14:53, Iain Sandoe wrote:
>> On 22 Feb 2023, at 14:11, Shengyu Huang via Gcc wrote:
>
> Possibly my bad - there are some additional fixes needed for newer Darwin on
> the 12 branch (I need to re-release 12.1 Darwin
Hi Shengyu,
> On 22 Feb 2023, at 14:11, Shengyu Huang via Gcc wrote:
>
>> IIRC I saw you post a few days ago about trying to build gcc on your M2
>> laptop; did you manage this? Building GCC trunk from a git checkout,
>> and hacking in a "hello world" warning would be a great place to start.
>>
Hi Shengyu,
> On 20 Feb 2023, at 17:31, Shengyu Huang via Gcc wrote:
>
> After following the instructions here
> (https://gcc.gnu.org/wiki/InstallingGCC) and here
> (https://gcc.gnu.org/install/index.html), the `make` step simply fails with
> “*** Configuration aarch64-apple-darwin22.1.0 not
> On 19 Feb 2023, at 16:27, -xlan- wrote:
>
> Hi, I have the SDK installed but I don't understand how to use the
> --with-sysroot command. Is the flag supposed to be with my make all-gcc
> command, please elaborate.
It is a configure argument for GCC’s configure script - there is more
info
Hi
> On 18 Feb 2023, at 20:28, -xlan- wrote:
>
> I tried compiling version 12.2.0 and it attempts to access system headers at
> /usr/include, but on mac the system headers are stored at
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include
> On 17 Feb 2023, at 15:37, Jonathan Wakely via Gcc wrote:
>
> On Fri, 17 Feb 2023, 15:17 -xlan- via Gcc, wrote:
>
>> I was building gcc version 4.9.1
>
>
> Why?
Indeed, what is the use-case?
trying to build such an old GCC version on modern macOS could be problematic.
> on Mac OS versio
> On 15 Dec 2022, at 05:58, chuanqi.xcq wrote:
>
> Hi Nathan,
>
> > But how do they specify the mapping from module/header-unit name to CMI, so
> > that
> > imports work?
> >
> > Is this really a clang-specific mechanism, as it has no module mapper ATM
> > (IIUC)?
>
> Yes, clang doesn't h
e ;
> ben.boeckel
> Subject:Re: Naming flag for specifying the output file name for Binary Module
> Interface files
>
> On 12/7/22 11:58, Iain Sandoe wrote:
> >
> >
> >> On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote:
> >>
> >> On 12/7
> On 7 Dec 2022, at 16:52, Nathan Sidwell via Gcc wrote:
>
> On 12/7/22 11:18, Iain Sandoe wrote:
>
>> I think it is reasonable to include c++ in the spelling, since other
>> languages supported by
>> GCC (and clang in due course) have modules.
>
> I dis
Hi Folks,
> On 7 Dec 2022, at 15:45, ben.boeckel via Gcc wrote:
>
> On Wed, Dec 07, 2022 at 15:23:09 +, Jonathan Wakely wrote:
>> I disagree. I can easily remember "module output" but I would have to check
>> the manual every time to see if it's "std c++ module save file" or some
>> other pe
Hi Paul,
> On 26 Nov 2022, at 18:06, Paul Koning via Gcc wrote:
>
>> On Nov 26, 2022, at 11:42 AM, Arnaud Charlet via Gcc wrote:
>>
The current statement (https://gcc.gnu.org/install/prerequisites.html) is:
GNAT
In order to build GNAT, the Ada compiler, you need a working
> On 26 Nov 2022, at 18:06, Paul Koning wrote:
>
>
>
>> On Nov 26, 2022, at 11:42 AM, Arnaud Charlet via Gcc wrote:
>>
>>
The current statement (https://gcc.gnu.org/install/prerequisites.html) is:
GNAT
In order to build GNAT, the Ada compiler, you need a working GNAT
> On 26 Nov 2022, at 16:42, Arnaud Charlet wrote:
>
>
>>> The current statement (https://gcc.gnu.org/install/prerequisites.html) is:
>>>
>>> GNAT
>>> In order to build GNAT, the Ada compiler, you need a working GNAT compiler
>>> (GCC version 5.1 or later).
>>>
>>> so, if 5.1 is not workin
Hi Paul,
> On 26 Nov 2022, at 15:48, Paul Koning via Gcc wrote:
>> On Nov 25, 2022, at 3:46 PM, Iain Sandoe wrote:
>>
>>> On 25 Nov 2022, at 20:13, Andrew Pinski via Gcc wrote:
>>>
>>> On Fri, Nov 25, 2022 at 12:08 PM Paul Koning wrote:
>&
Hi Paul,
> On 25 Nov 2022, at 20:13, Andrew Pinski via Gcc wrote:
>
> On Fri, Nov 25, 2022 at 12:08 PM Paul Koning wrote:
>>
>>> On Nov 25, 2022, at 3:03 PM, Andrew Pinski wrote:
>>>
>>> On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc
>>> wrote:
I'm trying to use fairly rec
Hi Paul,
> On 25 Nov 2022, at 20:08, Paul Koning via Gcc wrote:
>
>> On Nov 25, 2022, at 3:03 PM, Andrew Pinski wrote:
>>
>> On Fri, Nov 25, 2022 at 11:59 AM Paul Koning via Gcc wrote:
>>>
>>> I'm trying to use fairly recent GCC sources (the gcc-darwin branch to be
>>> precise) to build Ada
Hi Pete,
> On 25 Nov 2022, at 10:36, Peter Dyballa via Gcc wrote:
> On Mac OS X/macOS configure scripts leave conftest.dSYM subdirectories
> behind, created by dsymutil:
>
> checking for build system preprocessor... rm: conftest.dSYM: is a
> directory
> checking for build system e
> On 25 Nov 2022, at 09:11, LIU Hao via Gcc wrote:
>
> 在 2022/11/25 16:50, Marc Glisse 写道:
>> On Fri, 25 Nov 2022, LIU Hao via Gcc wrote:
>>> I am a Windows developer and I have been writing x86 and amd64 assembly for
>>> more than ten years. One annoying thing about GCC is that, for x86 if I
> On 9 Sep 2022, at 18:07, Ulrich Drepper via Gcc wrote:
>
> On Fri, Sep 9, 2022 at 5:26 PM Iain Sandoe wrote:
>
>> One small request, I realise that Python 2 is dead, but I regularly
>> bootstrap GCC
>> on older machines that only have Python 2 installations.
> On 7 Sep 2022, at 13:33, Martin Liška wrote:
>
> On 9/7/22 12:56, Richard Sandiford via Gcc wrote:
>> Ulrich Drepper via Gcc writes:
>>> I talked to Jonathan the other day about adding all the C++ library APIs to
>>> the name hint file now that the size of the table is not really a concern
> On 5 Sep 2022, at 09:53, Richard Biener via Gcc wrote:
>
> On Sun, Sep 4, 2022 at 3:33 PM Iain Sandoe wrote:
>>
>> Hi,
>>
>> I am clearly missing something here … can someone point out where it is?
>>
>> https://gcc.gnu.org/onlinedocs/
Hi,
I am clearly missing something here … can someone point out where it is?
https://gcc.gnu.org/onlinedocs/gcc-3.3/gcc/Variable-Attributes.html#Variable%20Attributes
in the discussion of applying this to structure fields:
"The aligned attribute can only increase the alignment; but you can decre
> On 22 Jul 2022, at 12:19, Sebastian Huber
> wrote:
>
> On 21.07.22 10:03, Iain Sandoe wrote:
>>> This sounds like an interesting approach in the long run, however, I need a
>>> short term solution which I can back port to GCC 10, 11, and
> On 21 Jul 2022, at 06:25, Sebastian Huber
> wrote:
>
> On 20.07.22 15:01, Alexander Monakov wrote:
>> On Wed, 20 Jul 2022, Sebastian Huber wrote:
>>> On 20/07/2022 13:41, Alexander Monakov wrote:
On Wed, 20 Jul 2022, Sebastian Huber wrote:
> How does Ada get its default TLS m
, it would be good to establish if there is a meaningful use-case
for libgccjit in a cross-compiler, and if so fix the configuration - or (if no
meaningful use-case) exclude it as per the patch.
thanks
Iain
> On 26 Jun 2022, at 14:06, Iain Sandoe wrote:
>
> Hi Dave, folks,
>
>
Hi Dave, folks,
It seems to me that it is plausible that one could use the JIT in a
heterogenous system, e.g. an x86_64-linux-host with some kind of co-processor
which is supported as a GCC target (and therefore can be loaded with jit-d
code) … but I’m not aware of anyone actually doing this?
> On 23 Jun 2022, at 16:40, Iain Sandoe via Gcc wrote:
>
>
>
>> On 23 Jun 2022, at 07:51, Iain Sandoe via Gcc wrote:
>>
>>> On 23 Jun 2022, at 05:24, Bruno Haible wrote:
>>>
>>> Iain Sandoe wrote:
>>
>>>> … although n
> On 23 Jun 2022, at 07:51, Iain Sandoe via Gcc wrote:
>
>> On 23 Jun 2022, at 05:24, Bruno Haible wrote:
>>
>> Iain Sandoe wrote:
>
>>> … although now I see some configure warnings about not being able to access
>>> build-aux (which I do n
Hi Jakub,
> On 21 Jun 2022, at 12:33, Jakub Jelinek via Gcc wrote:
>
> The first release candidate for GCC 10.4 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/10.4.0-RC-20220621/
> ftp://gcc.gnu.org/pub/gcc/snapshots/10.4.0-RC-20220621/
>
> and shortly its mirrors. It has been ge
Hi Bruno,
> On 23 Jun 2022, at 05:24, Bruno Haible wrote:
>
> Iain Sandoe wrote:
>> … although now I see some configure warnings about not being able to access
>> build-aux (which I do not recall seeing with the previous hack - but that
>> could be just bad m
Hi Bruno,
+1 on the C reasons for removing intl.
(however, once we have a rough working patch, it would still need buy-in from
GDB + binutils)
> On 21 Jun 2022, at 03:05, Bruno Haible wrote:
>> So, indeed, part of this is quite straight forward - we can amend the
>> Makefile.def
>> to specify
Hi Bruno,
> On 19 Jun 2022, at 09:40, Iain Sandoe via Gcc wrote:
>
>> On 19 Jun 2022, at 01:32, Bruno Haible wrote:
>>> - so, please could we follow the pattern for GMP et. al. where the library
>>> can be provided with —with-intl= pointing to an installatio
Hi Bruno,
> On 19 Jun 2022, at 01:32, Bruno Haible wrote:
>
> Iain Sandoe wrote:
>> As a maintainer for GCC on a non-glibc system, I would:
>> (b) not want to [force] add a shared lib dependency for my downstream.
>
> In order to avoid shared libs, the user me
Hi Bruno,
> On 18 Jun 2022, at 18:01, Bruno Haible wrote:
> As the long-term GNU gettext maintainer, I would suggest to remove the intl/
> directory from the GCC distribution.
>
> The effect for the users would be:
> * On systems without glibc, users who want an internationalized GCC
>inst
Hi.
My ‘downstream’ have a situation in which they make use of a directory outside
of the configured GCC installation - and symlink from there to libraries in the
actual install tree.
e.g.
/foo/bar/lib:
libgfortran.dylib -> /gcc/install/path/lib/libgfortran.dylib
Now I want to find a way fo
> On 23 May 2022, at 07:50, Iain Sandoe wrote:
>
> Hi Richard,
>
>> On 23 May 2022, at 07:27, Richard Biener wrote:
>>
>> On Sun, 22 May 2022, Iain Sandoe wrote:
>>
>>> Hi
>>>
>>>> On 20 May 2022, at 09:02, Richard Biener
Hi Richard,
> On 23 May 2022, at 07:27, Richard Biener wrote:
>
> On Sun, 22 May 2022, Iain Sandoe wrote:
>
>> Hi
>>
>>> On 20 May 2022, at 09:02, Richard Biener via Gcc wrote:
>>
>>> The first release candidate for GCC 9.5 is available from
&
Hi
> On 20 May 2022, at 09:02, Richard Biener via Gcc wrote:
> The first release candidate for GCC 9.5 is available from
>
> https://sourceware.org/pub/gcc/snapshots/9.5.0-RC-20220520/
>
> and shortly its mirrors. It has been generated from git commit
> 1bc79c506205b6a5db82897340bdebaaf7ada93
Hi Ankur,
> On 8 May 2022, at 15:29, Ankur Saini via Gcc wrote:
>
> I have been fiddling around with the patch regarding "bypassing assmebler
> while generating slim lto files" and managed to make it build with the
> current trunk. Though the patch seems to be working on Linux machine, it
> cau
Hi Jakub,
thanks for doing the release.
> On 29 Apr 2022, at 15:34, Jakub Jelinek via Gcc wrote:
>
> The first release candidate for GCC 12.1 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/
> ftp://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/
>
> and shortl
> On 22 Apr 2022, at 15:08, Boris Kolpackov wrote:
>
> Ben Boeckel writes:
>
>> On Thu, Apr 21, 2022 at 06:05:52 +0200, Boris Kolpackov wrote:
>>
>>> I don't think it is. A header unit (unlike a named module) may export
>>> macros which could affect further dependencies. Consider:
>>>
>>>
> On 21 Apr 2022, at 19:08, Ben Boeckel wrote:
>
> On Thu, Apr 21, 2022 at 18:59:56 +0100, Iain Sandoe wrote:
>> Hi Ben,
>>
>>> On 21 Apr 2022, at 13:05, Ben Boeckel via Gcc wrote:
>>>
>>> On Thu, Apr 21, 2022 at 06:05:52 +0200, Boris Kol
Hi Ben,
> On 21 Apr 2022, at 13:05, Ben Boeckel via Gcc wrote:
>
> On Thu, Apr 21, 2022 at 06:05:52 +0200, Boris Kolpackov wrote:
>> I don't think it is. A header unit (unlike a named module) may export
>> macros which could affect further dependencies. Consider:
>>
>> import "header-unit.hpp";
> On 12 Apr 2022, at 13:31, Martin Liška wrote:
>
> On 4/12/22 11:58, Richard Biener wrote:
>> On Tue, Apr 12, 2022 at 11:20 AM Jan Hubicka via Gcc wrote:
>>>
>>> Hi,
> On 08-Apr-2022, at 6:32 PM, Jan Hubicka wrote:
>
> Ankur,
>> I was browsing the list of submi
Hi Shivam,
> On 2 Apr 2022, at 17:48, Shivam Gupta wrote:
>
> May I ask why we need to specify --with-gxx-libcxx-include-dir= at
> compile/configure time of GCC?
The libc++ headers are not part of a base system install (on Darwin they are
part of either Xcode or Command Line Tools installat
Hi Shivam,
> On 2 Apr 2022, at 06:57, Shivam Gupta wrote:
>
> I saw your last year's mail for the same topic on the GCC mailing list
> -https://gcc.gnu.org/pipermail/gcc/2020-March/000230.html.
The patch was applied to GCC-11 (so is available one GCC-11 branch and will be
on GCC-12 when that
Hi Richard,
> On 20 Jan 2022, at 22:32, Richard Sandiford wrote:
>
> Iain Sandoe writes:
>>> On 10 Jan 2022, at 10:46, Richard Sandiford
>>> wrot>> An alternative might be to make promote_function_arg a “proper”
>>> ABI hook, taking a cumulative_a
Hi FX,
> On 15 Jan 2022, at 14:19, FX via Gcc wrote:
>
>> The purpose of these asm tests is to verify that the analyzer doesn't
>> get confused by various inline assembler directives used in the source
>> of the Linux kernel. So in theory they ought to work on any host, with
>> a gcc configured
Hi Florian,
> On 10 Jan 2022, at 08:38, Florian Weimer wrote:
>
> * Jeff Law via Gcc:
>
>> Most targets these days use registers for parameter passing and
>> obviously we can run out of registers on all of them. The key
>> property is the size/alignment of the argument differs depending on if
> On 10 Jan 2022, at 10:46, Richard Sandiford wrote:
>
> Iain Sandoe writes:
>> Hi Folks,
>>
>> In the aarch64 Darwin ABI we have an unusual (OK, several unusual) feature
>> of the calling convention.
>>
>> When an argument is passed *in a regi
Hi Folks,
In the aarch64 Darwin ABI we have an unusual (OK, several unusual) feature of
the calling convention.
When an argument is passed *in a register* and it is integral and less than SI
it is promoted (with appropriate signedness) to SI. This applies when the
function parm is named only.
> On 7 Jan 2022, at 12:55, Martin Liška wrote:
>
> On 1/7/22 12:05, Jonathan Wakely via Gcc wrote:
>> References to .cc files in the commit message won't get changed to .c
>> automatically, but maybe the gcc-backport alias could be taught to do
>> that.
> +1 for me. I'm willing to extend gcc-
> On 15 Dec 2021, at 12:29, Jonathan Wakely via Gcc wrote:
>
> On Wed, 15 Dec 2021 at 12:22, Tobias Burnus wrote:
>>
>> On 15.12.21 12:39, Jonathan Wakely via Gcc wrote:
>>
>>> Iain pointed out a drawback of not having the regression info in the
>>> Summary. Currently it does draw your atten
> On 9 Oct 2021, at 10:11, Thomas Koenig wrote:
>
>
> On 09.10.21 01:18, Iain Sandoe wrote:
>>> I meant the case where the user writes, with an old, KIND=16 is double
>>> double compiler,
>>>
>>> subroutine foo(a)
>>>real(k
> On 8 Oct 2021, at 23:55, Thomas Koenig via Gcc wrote:
>
>
> Hi Iain,
>
>>> Things get interesting for user code, calling a routine compiled
>>> for double double with newer IEEE QP will result in breakage.
>> That would not happen with the proposal above, since the library would
>> have di
Hi Thomas,
recognising that this is complex - the intent here is to see if there are ways
to partition the problem (where the pain falls does depend on the choices
made).
perhaps:
*A library (interface, name)
*B compiler internals
*C user-facing changes
> On 8 Oct 2021, at 17:26, Thomas K
> On 8 Oct 2021, at 07:35, Thomas Koenig via Fortran
> wrote:
>
>
> On 07.10.21 17:33, Jakub Jelinek wrote:
>>> It will also be a compatibility issue if users have code compiled on a LE
>>> system with GCC 11 and earlier with KIND=16, it will not link with GCC 12.
>> libgfortran ABI changed
Folks,
As many of you know, Apple has now released an AArch64-based version of macOS
and desktop/laptop platforms using the ‘M1’ chip to support it. This is in
addition to the existing iOS mobile platforms (but shares some of their
constraints).
There is considerable interest in the user-base
Hi Marc,
> On 23 Jul 2021, at 08:30, Marc wrote:
>
> Thank you so far, this got me (unsurprisingly) one step further, but
> then the external function resolve error is moved to the library loading
> stage:
>
> ~/afl++ $ g++-11 -Wl,-flat_namespace -Wl,-undefined,dynamic_lookup -g
> -fPIC -std=c+
> On 22 Jul 2021, at 20:41, Andrew Pinski via Gcc wrote:
>
> On Thu, Jul 22, 2021 at 7:37 AM Marc wrote:
>>
>> I have a gcc plugin (for afl++,
>> https://github.com/AFLplusplus/AFLplusplus) that works fine when
>> compiled on Linux but when compiled on MacOS (brew install gcc) it fails:
>>
1 - 100 of 205 matches
Mail list logo
