Re: Can't build Ada

> 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

Re: Can't build Ada

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

Re: Naming flag for specifying the output file name for Binary Module Interface files

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

Re: Naming flag for specifying the output file name for Binary Module Interface files

> 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

Re: Naming flag for specifying the output file name for Binary Module Interface files

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

Re: Naming flag for specifying the output file name for Binary Module Interface files

> 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

Re: Failure During Building

> 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

Re: Failure During Building

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

Re: Failure During Building

> 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

Re: [GSoC] Help needed for building on aarch64-apple-darwin22.1.0

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

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

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. >>

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

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

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

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

Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on

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

Question on aarch64 prologue code.

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

Re: Question on aarch64 prologue code.

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

Re: gcc-12+: D / phobos runtime

> 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

Re: [PATCH] Fix coroutine tests for libstdc++ gnu-version-namespace mode

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

Re: [PATCH] Fix coroutine tests for libstdc++ gnu-version-namespace mode

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 >>>

Re: Hints on reconfiguring GCC

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

Arm assembler crc issue

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

Re: Arm assembler crc issue

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

Re: Arm assembler crc issue

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

Re: New TLS usage in libgcc_s.so.1, compatibility impact

> 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

Re: [Request for Comments] Using Rust libraries in the Rust frontend

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

Re: Question about information from -fdump-rtl-sched2 on M1 Max

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

Re: Question about information from -fdump-rtl-sched2 on M1 Max

> 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

Re: isl 0.26 C++17 issues when bootstrapping with GCC

> 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 >>&

Re: isl 0.26 C++17 issues when bootstrapping with GCC

> 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

Re: isl 0.26 C++17 issues when bootstrapping with GCC

> 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

About the effect of "O0" on inlining into a function.

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?

Re: About the effect of "O0" on inlining into a function.

> 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

Re: About the effect of "O0" on inlining into a function.

> 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

Re: About the effect of "O0" on inlining into a function

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

Re: GCC 11.5 Release Candidate available from gcc.gnu.org

> 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

Re: Bugs in GCC 14.2 …/fixed-include/ files

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

Re: Bugs in GCC 14.2 …/fixed-include/ files

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

On the subject of module consumer diagnostics.

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

Re: On the subject of module consumer diagnostics.

> 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. >

Re: On the subject of module consumer diagnostics.

> 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

Re: [RFH] Uses of output.h in the front ends

Hi Steven, On 4 Jun 2012, at 13:40, Steven Bosscher wrote: > > asm_out_file for NEXT runtime ABI v01: > objc/objc-next-runtime-abi-01.c:#include "output.h" /* for asm_out_file */ > objc/objc-next-runtime-abi-01.c: ASM_DECLARE_UNRESOLVED_REFERENCE > (asm_out_file, string); > objc/objc-next-runtim

Re: [RFH] Uses of output.h in the front ends

Hi Steven, On 5 Jun 2012, at 19:01, Steven Bosscher wrote: > On Tue, Jun 5, 2012 at 4:15 PM, Iain Sandoe wrote: >> As it happens, the code should be as well-tested as for V1 as V2 ABI - >> since it is conventional to test ObjC/NeXT at m32(V1) and m64(V2) [[and >> also the G

Re: [RFH] Uses of output.h in the front ends

Hi Steven, On 5 Jun 2012, at 21:23, Steven Bosscher wrote: > On Tue, Jun 5, 2012 at 8:55 PM, Iain Sandoe wrote: >> I would welcome a simple solution if one is available, although I don't >> quite see what you have in mind at present. > > This is what I have in mind.

examples of (so called) time-travel optimisations in GCC?

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

Re: On pull request workflows for the GNU toolchain

> 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

Re: GCC 9.3 Release Candidate available from gcc.gnu.org

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

Changes in Mail-list to Web integration.

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

Re: GCC 10.1 Release Candidate available from gcc.gnu.org

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

Re: [1-800-GIT-HELP] Backporting a series of commits into a combined commit?

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

Re: WWDC thread: support for darwin/macOS going forward

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

Re: GCC 10.2 Release Candidate available from gcc.gnu.org

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

Re: Question about interpreting a decl dump

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

Question about whether a code fragment is expected to parse.

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" __

Re: Question about whether a code fragment is expected to parse.

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__((__vi

Re: [1-800-GIT-HELP] Pushing a merge with master to a branch fails with git gcc-verify

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

Re: gcc/DATESTAMP not updated any longer

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

Re: gcc/DATESTAMP not updated any longer

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

Re: Query about compatibility

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 (

Re: Erroneous results from gfortran

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

Re: GCC 10.3 Release Candidate available from gcc.gnu.org

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

Re: GCC 10.3 Release Candidate available from gcc.gnu.org

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

Re: removing toxic emailers

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

Re: removing toxic emailers

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

Re: Need help debugging possible 10.3 bad code generation regression from 10.2/9.3 on Mac OS 10.15.7 (Catalina)

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

Re: D build on powerpc broken (was Re: GCC 11.1 Release Candidate available from gcc.gnu.org)

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

Re: "musttail" statement attribute for GCC?

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

Re: Second GCC 11.1 Release Candidate available from gcc.gnu.org

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://

Re: "musttail" statement attribute for GCC?

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

Re: GCC 8.5 Release Candidate available from gcc.gnu.org

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

Re: GCC 9.4 Release Candidate available

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

Re: [Patch] contrib/mklog.py: Improve PR handling

> 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

Re: [Patch] contrib/mklog.py: Improve PR handling (was: git gcc-commit-mklog doesn't extract PR number to ChangeLog)

> 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)

Re: Disabling TLS address caching to help QEMU on GNU/Linux

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

Re: GCC 11.2 Release Candidate available

> 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. >

Re: gcc plugin on MacOS failure

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

Re: gcc plugin on MacOS failure

> 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: >>

Re: gcc plugin on MacOS failure

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+

Re: Labelling of regressions in Bugzilla

> 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

Re: Mass rename of C++ .c files to .cc suffix?

> 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-

Re: [GSoC]Bypass assembler when generating LTO object files

> 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

Re: [modules] Preprocessing requires compiled header unit modules

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";

Re: [modules] Preprocessing requires compiled header unit modules

> 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

Re: GCC 12.1 Release Candidate available from gcc.gnu.org

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

Re: Updating patch regarding bypassing assembler when generating LTO object files

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

Re: remove intl/ directory?

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

Re: remove intl/ directory?

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

Re: remove intl/ directory?

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

Re: remove intl/ directory?

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

Re: remove intl/ directory?

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

Re: remove intl/ directory?

> 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

Re: remove intl/ directory?

> 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

Re: Use -ftls-model=local-exec for RTEMS by default?

> 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

Re: Use -ftls-model=local-exec for RTEMS by default?

> 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

Re: [RFC] database with API information

> 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

Re: [RFC] database with API information

> 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.

Re: End of subscription

> 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

Re: How to compress the size of a field in a structure?

> 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; >

Re: Analyzer test failures

> 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

Re: GCC 14.1 Release Candidate available from gcc.gnu.org

> 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

Re: Second GCC 14.1 Release Candidate available from gcc.gnu.org

> 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

<    1   2   3   >