> 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
> 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
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 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
> 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;
>
> 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
> 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. If possible (and
>> it sounds
> 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 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 12. I guess I
>>> will add a
>>>
>>> MULTILIB_EXTR
> 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
> 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 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 memory ;) )
>
> You can get warnin
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 merely has to pass the option
> '--d
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 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 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 Kolpackov wrote:
I don't think it is. A header unit
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
> 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
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:
>>
Hi Marc,
> On 22 Jul 2021, at 15:34, 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:
>
> ~/afl++ $ g++-11 -g -fPIC -std=c++11
> -I/usr/local/Cellar/gcc/1
> On 21 Jul 2021, at 10:02, Richard Biener wrote:
>
>
> The first release candidate for GCC 11.2 is available from
>
> https://sourceware.org/pub/gcc/snapshots/11.2-RC-20210721/
>
> and shortly its mirrors. It has been generated from git commit
> 076930b9690ac3564638636f6b13bbb6bc608aea.
>
Hi Florian,
This also affects fibres implementations (both C++ and D ones at least from
discussion with both communities).
> On 20 Jul 2021, at 15:52, Florian Weimer via Gcc wrote:
>
> Currently, the GNU/Linux ABI does not really specify whether the thread
> pointer (the address of the TCB) may
> On 21 Jun 2021, at 08:26, Martin Liška wrote:
>
> On 6/21/21 8:42 AM, Tobias Burnus wrote:
>> On 18.06.21 16:41, Jason Merrill wrote:
>>>
>>> * Being able to specify the PR numbers on the command line in addition
>>>(currently, they are only extracted from the testsuite patches)
> On 18 Jun 2021, at 17:47, Martin Sebor via Gcc wrote:
>
> On 6/18/21 8:41 AM, Jason Merrill via Gcc wrote:
>> On Fri, Jun 18, 2021 at 7:06 AM Tobias Burnus
>> wrote:
>>> On 18.06.21 11:32, Richard Earnshaw via Gcc wrote:
On 17/06/2021 18:21, Jakub Jelinek wrote:
> mklog as is doesn
Richard Biener wrote:
The first release candidate for GCC 9.4 is available from
https://sourceware.org/pub/gcc/snapshots/9.4.0-RC-20210519/
and shortly its mirrors. It has been generated from git commit
8091c46cf736124a106922ddfd1fdb99f33b0241.
I have so far bootstrapped and tested the rel
William Seurer via Gcc wrote:
On 5/7/21 2:48 PM, Jakub Jelinek via Gcc wrote:
The first release candidate for GCC 8.5 is available from
https://gcc.gnu.org/pub/gcc/snapshots/8.5.0-RC-20210507/
ftp://gcc.gnu.org/pub/gcc/snapshots/8.5.0-RC-20210507
and shortly its mirrors. It has been gener
Alexander Monakov wrote:
On Fri, 23 Apr 2021, Josh Haberman via Gcc wrote:
On Fri, Apr 23, 2021 at 1:10 PM Iain Sandoe
wrote:
I did try to use it this ^ for GCC coroutines (where such a guarantee is
pretty important)
However, the issue there is that not all targets support indirect
tail
William Seurer via Gcc wrote:
On 4/23/21 8:31 AM, Jakub Jelinek via Gcc wrote:
Some blocker bugs were reported against the first release candidate
of GCC 11.1, so there is a second release candidate for GCC 11.1
available from
https://gcc.gnu.org/pub/gcc/snapshots/11.1.0-RC-20210423/
ftp://
David Malcolm via Gcc wrote:
On Fri, 2021-04-23 at 12:44 -0700, Josh Haberman via Gcc wrote:
Would it be feasible to implement a "musttail" statement attribute in
GCC to get a guarantee that tail call optimization will be performed?
Such an attribute has just landed in the trunk of Clang
(htt
Peter Bergner via Gcc wrote:
On 4/20/21 4:20 PM, Jakub Jelinek via Gcc wrote:
On Tue, Apr 20, 2021 at 03:27:08PM -0500, William Seurer via Gcc wrote:
/tmp/cc8zG8DV.s: Assembler messages:
/tmp/cc8zG8DV.s:2566: Error: unsupported relocation against r13
/tmp/cc8zG8DV.s:2570: Error: unsupported r
Lucier, Bradley J via Gcc wrote:
I’m seeing an “Illegal Instruction” fault and don’t quite know how to
generate a proper bug report yet.
This is the compiler:
[Bradleys-Mac-mini:~] lucier% /usr/local/gcc-10.3.0/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/usr/local/gcc-10.3.0/bin/gcc
COLLE
Kalamatee wrote:
On Fri, 16 Apr 2021 at 11:05, Kalamatee wrote:
On Fri, 16 Apr 2021 at 10:42, Iain Sandoe via Gcc wrote:
It is already a considerable leap for many engineers to post code for
public
review; it is essential (IMO) that review of code is carried out on a fair
and
Ian Lance Taylor via Gcc wrote:
On Thu, Apr 15, 2021 at 8:02 PM Frosku wrote:
We want free software to succeed. Free software is more likely to
succeed if more people work on it. If you are a volunteer, as many
are, you can choose to spend your time on the project where you have
to short-stop
Jonathan Wakely via Gcc wrote:
On Sat, 3 Apr 2021 at 00:53, Richard Copley via Gcc
wrote:
On 01/04/2021 13:35, Richard Biener wrote:
The first release candidate for GCC 10.3 is available from
https://gcc.gnu.org/pub/gcc/snapshots/10.3.0-RC-20210401/
ftp://gcc.gnu.org/pub/gcc/snapshots/10
Richard Biener wrote:
On April 1, 2021 4:08:21 PM GMT+02:00, Eric Botcazou
wrote:
I have so far bootstrapped and tested the release candidate on
x86_64-linux. Please test it and report any issues to bugzilla.
On x86 Darwin, a lot of new libstdc++ experimental/filesystem fails.
https://gc
Hello Professor,
Shahrooz, Bahram (shahrobm) via Gcc wrote:
I’ve used gfortran to compile a program on Mac Big Sur using gcc-10.2 and
on Windows 10 using g77. I’ve used -o0 for both cases. The results for
identical input values are vastly different between the two executables
and wrong
Chirumamilla Ganesh via Gcc wrote:
Does M1 MacBooks support GCC compilers ,if not will M1 MacBooks ever get
compatibility of GCC compilers
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168
and https://github.com/iains/gcc-darwin-arm64
This is experimental at present, support for macOS (
Iain Sandoe via Gcc wrote:
Jakub Jelinek via Gcc wrote:
On Fri, Nov 06, 2020 at 08:56:25PM +0100, Richard Biener wrote:
Darwin: Darwin 20 is to be macOS 11 (Big Sur).
So, I'm afraid it must fail or bypass this code path somewhere earlier
in the hooks.
Is that maybe already known t
Jakub Jelinek via Gcc wrote:
On Fri, Nov 06, 2020 at 08:56:25PM +0100, Richard Biener wrote:
Darwin: Darwin 20 is to be macOS 11 (Big Sur).
So, I'm afraid it must fail or bypass this code path somewhere earlier
in the hooks.
Is that maybe already known to the repo when it is on some rebase
Thomas Koenig via Gcc wrote:
I tried to update the coarray_native branch to current master with
"git merge master" as given by
https://gcc.gnu.org/gitwrite.html#branches
That worked without any error message.
Next, I tried to verify that a "git push" would succeed, and
got an error:
$ git g
Nathan Sidwell wrote:
On 10/26/20 7:08 AM, Nathan Sidwell wrote:
On 10/25/20 7:52 AM, Iain Sandoe wrote:
Given that GNU attributes are not part of the standard..
I wonder if the following is expected to work?
__attribute__((__deprecated__))
extern "C" __attribute__((__visibility__("defaul
Hi
Given that GNU attributes are not part of the standard..
I wonder if the following is expected to work?
__attribute__((__deprecated__))
extern "C" __attribute__((__visibility__("default")))
void foo ()
{
}
t.C:3:8: error: expected unqualified-id before string constant
3 | extern "C" __
Thomas Koenig via Fortran wrote:
and the library function has
mmaxloc2_4_s1 (gfc_array_s1 * const restrict array,
gfc_array_l1 * const restrict mask,
GFC_LOGICAL_4 back,
gfc_charlen_type len)
As far as I can tell, the decl loo
Richard Biener wrote:
The first release candidate for GCC 10.2 is available from
https://gcc.gnu.org/pub/gcc/snapshots/10.2.0-RC-20200715/
ftp://gcc.gnu.org/pub/gcc/snapshots/10.2.0-RC-20200715/
and shortly its mirrors. It has been generated from git commit
932e9140d3268cf2033c1c3e93219541c
Hey Eric,
Eric Gallager via Gcc wrote:
Hi, at Apple's WWDC this year they have announced that they are doing
yet another architecture transition, so I was wondering what exactly
would be the best way to go about adding support for it? The first
issue would be just what to call the new architec
Jonathan Wakely via Gcc wrote:
On Mon, 1 Jun 2020 at 13:25, Thomas Koenig wrote:
Am 01.06.20 um 14:20 schrieb Jonathan Wakely via Gcc:
It will only "keep" it for a matter of seconds, between that
backported commit and the backported fix. And unless you push the
first commit before pushing th
Jakub Jelinek via Gcc wrote:
The first release candidate for GCC 10.1 is available from
https://gcc.gnu.org/pub/gcc/snapshots/10.1.0-RC-20200430/
ftp://gcc.gnu.org/pub/gcc/snapshots/10.1.0-RC-20200430
and shortly its mirrors. It has been generated from git revision
r10-8080-g591d857164c37cd0
Hi Folks,
thanks for the work to migrate to the new server.
In the transition, I observe some changes to the integration of mail with
the web-pages.
In particular, my existing links seem to point now to:
https://gcc.gnu.org/legacy-ml/gxxx
If I reconnect from the GCC front page, f
Jakub Jelinek wrote:
The first release candidate for GCC 9.3 is available from
https://gcc.gnu.org/pub/gcc/snapshots/9.3.0-RC-20200305/
ftp://gcc.gnu.org/pub/gcc/snapshots/9.3.0-RC-20200305/
and shortly its mirrors. It has been generated from git commit
r9-8351-ge50627ff8cd54c3983614b3472732
60 matches
Mail list logo
