Re: GCC does not optimize well enough with vectors on bitshift

While this doesn't affect your example in this particular case: please don't use `-march-native` on Compiler Explorer for these examples - this will pick whatever architecture your individual query is served from which may be any of the available AMD or Intel CPUs we run on. There ought to be a pop

Re: GCC does not optimize well enough with vectors on bitshift

Correct link is https://godbolt.org/z/GfeTobMvs On Mon, Mar 10, 2025 at 4:45 PM Qwert Nerdish wrote: > On this godbolt link at https://godbolt.org/z/GfeTobMvs, the two C source > codes behave identical. > Yet the second source code does not use vectors and is 30% slower when I > tested it. >

Re: GCC does not optimize well enough with vectors on bitshift

Thanks for the report! Please file it at https://gcc.gnu.org/bugzilla/enter_bug.cgi?product=gcc On Mon, Mar 10, 2025 at 10:47 AM Qwert Nerdish via Gcc > wrote: > > > Correct link is https://godbolt.org/z/GfeTobMvs > > > > On Mon, Mar 10, 2025 at 4:45 PM Qwert Nerdish > > wrote: > > > > > On thi

Re: gcc-git-customization.sh error

On Wed, 5 Mar 2025 at 14:05, Richard Earnshaw (lists) wrote: > > On 05/03/2025 13:47, Jonathan Wakely wrote: > > On Wed, 5 Mar 2025 at 13:37, Richard Earnshaw (lists) > > wrote: > >> > >> On 05/03/2025 13:10, Jonathan Wakely via Gcc wrote: > >>> While onboarding somebody today we noticed an error

Re: gcc-git-customization.sh error

On 05/03/2025 13:47, Jonathan Wakely wrote: > On Wed, 5 Mar 2025 at 13:37, Richard Earnshaw (lists) > wrote: >> >> On 05/03/2025 13:10, Jonathan Wakely via Gcc wrote: >>> While onboarding somebody today we noticed an error in the >>> customization script if you use a non-default value for the loca

Re: gcc-git-customization.sh error

On Wed, 5 Mar 2025 at 13:37, Richard Earnshaw (lists) wrote: > > On 05/03/2025 13:10, Jonathan Wakely via Gcc wrote: > > While onboarding somebody today we noticed an error in the > > customization script if you use a non-default value for the local > > prefix. > > > > I reproduced it with bash -x

Re: gcc-git-customization.sh error

On 05/03/2025 13:10, Jonathan Wakely via Gcc wrote: > While onboarding somebody today we noticed an error in the > customization script if you use a non-default value for the local > prefix. > > I reproduced it with bash -x to show where it happens. In the output > below I entered "jw" as the loca

Re: GCC GSoC 2025: Call for project ideas and mentors

Hello everyone, I am pleased that I can announce that we have been accepted to be a GSoC mentoring organization also in 2025!. This also means that students are now really starting to look at our idea page and so if anyone wants to add a project, it is still possible but we should not delay it mu

Re: gcc 3.2.3 i370 with z/PDOS-generic and mfemul

> But I have a new emulator called mfemul.c, and it > isn't very mature and almost certainly has a bug in > it that is affecting gcc 3.2.3. And since that is the only > Any suggestions on where to stick some printfs so that > I can start looking for a divergence, given that the > generated code is

Re: GCC used to store pointers in FP registers on aarch64

On Mon, Feb 24, 2025 at 10:46:42AM +0100, Attila Szegedi wrote: > Hi folks, Hi, I've been pointed at this thread due to the reference to my Linux patch series fixing some KVM FPSIMD/SVE/SME issues. > I'm looking for a bit of a historic context for a fun GCC behavior we > stumbled across. For...

Re: GCC used to store pointers in FP registers on aarch64

On Mon, Feb 24, 2025 at 1:21 PM Florian Weimer wrote: > * Attila Szegedi: > > >> That seems … quite unlikely. GCC 8 has seen extensive use on > >> AArch64, on a variety of implementations, and I don't recall > >> problems in this area. I don't follow AArch64 *that* closely, > >> admittedly, but

Re: GCC used to store pointers in FP registers on aarch64

* Attila Szegedi: >> That seems … quite unlikely. GCC 8 has seen extensive use on >> AArch64, on a variety of implementations, and I don't recall >> problems in this area. I don't follow AArch64 *that* closely, >> admittedly, but I expect it would have caused quite a ruckus. >> > > Yeah. The lac

Re: GCC used to store pointers in FP registers on aarch64

On Mon, Feb 24, 2025 at 12:41 PM Florian Weimer wrote: > > Surely not preserving floating point bit patterns in registers would > be a silicon bug? Indeed it would be. > That seems … quite unlikely. GCC 8 has seen > extensive use on AArch64, on a variety of implementations, and I don't > rec

Re: GCC used to store pointers in FP registers on aarch64

* Attila Szegedi via Gcc: > We noticed that this version of GCC compiling on aarch64 will happily use > FP registers to temporarily store/load pointers, so there'd be "fmov d9, > x1" to store a pointer, and then later when it's used as a parameter to a > function call we'll see "fmov x1, d9" etc.

Re: GCC used to store pointers in FP registers on aarch64

Hi Attila, > On 24 Feb 2025, at 10:46, Attila Szegedi via Gcc wrote: > > Hi folks, > > I'm looking for a bit of a historic context for a fun GCC behavior we > stumbled across. For... reasons we build some of our binaries using an > older version of GCC (8.3.1, yes, we'll be upgrading soon, and

Re: GCC for C6x DSPs

Hi again, Richard probably knows this but the gcc docs from the git master have this: '-march=NAME' This specifies the name of the target architecture. GCC uses this name to determine what kind of instructions it can emit when generating assembly code. Permissible names are: 'c

Re: GCC for C6x DSPs

On Tue, Feb 18, 2025 at 3:04 AM Richard Biener via Gcc wrote: > On Tue, Feb 18, 2025 at 7:10 AM Dan via Gcc wrote: > > > > Hello! > > > > I'm trying to compile for Texas Instruments (TI) C6000 Digital Signal > > Processor (DSP) using GCC. I'm aware that TI has its own compiler, but I > > want to

Re: GCC for C6x DSPs

On Tue, Feb 18, 2025 at 7:10 AM Dan via Gcc wrote: > > Hello! > > I'm trying to compile for Texas Instruments (TI) C6000 Digital Signal > Processor (DSP) using GCC. I'm aware that TI has its own compiler, but I > want to use GCC. > > The documentation indicates that GCC has *some* support for C6x

Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB

Thank you so much. It helps. I apologize for adding other email lists. I will make sure to handle this more effectively in future communications. On Mon, Feb 3, 2025 at 10:36 AM Andrew Pinski wrote: > On Sun, Feb 2, 2025 at 8:57 PM Geeta Dora > wrote: > > > > Thank you. I wanted to mention th

Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB

On Sun, Feb 2, 2025 at 8:57 PM Geeta Dora wrote: > > Thank you. I wanted to mention that on Linux, even when using a response > file, we still encounter the same issue if the response file exceeds 128KB in > size. > > Does this imply that GCC enforces a limit on individual command-line > argu

Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB

Thank you. I wanted to mention that on Linux, even when using a response file, we still encounter the same issue if the response file exceeds 128KB in size. Does this imply that GCC enforces a limit on individual command-line arguments (including those in response files) such that no argument sh

Re: GCC Fails to Compile When Command Line Argument Size Exceeds 128KB

On Sun, Feb 2, 2025 at 8:31 PM Geeta Dora via Gcc-bugs wrote: > > Dear GCC Developers, > > I encountered an issue where GCC fails to compile when the total > command-line argument > size exceeds 128KB. > > In contrast, Clang can handle the same compilation scenario without issues. > > Is this a kn

Re: GCC devroom at FOSDEM 2025?

"James K. Lowden" writes: Hello James, > I went to https://pretalx.fosdem.org/fosdem-2025/cfp today. It says > the deadline isn't the 15th, but was yesterday! Am i really too > late? Dec 15th is for the schedule announcement: we have ~15 days to read all the proposals and decide which one we

Re: GCC devroom at FOSDEM 2025?

Hi James! On 2024-12-01T17:34:13-0500, "James K. Lowden" wrote: > On Tue, 01 Oct 2024 11:48:34 +0200 > Thomas Schwinge wrote: > >> I need two, three people as co-organizers: >> for evaluating submissions (before 2024-12-15), > > I went to https://pretalx.fosdem.org/fosdem-2025/cfp today. It sa

Re: GCC devroom at FOSDEM 2025?

On Tue, 01 Oct 2024 11:48:34 +0200 Thomas Schwinge wrote: > I need two, three people as co-organizers: > for evaluating submissions (before 2024-12-15), Hi Thomas, I went to https://pretalx.fosdem.org/fosdem-2025/cfp today. It says the deadline isn't the 15th, but was yesterday! Am i reall

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

Hi Gerald, On Mon, Dec 02, 2024 at 12:13:35AM +0100, Gerald Pfeifer wrote: > On Sun, 1 Dec 2024, Alexander Monakov wrote: > > You have to use the name of the branch in the remote repo, > > "python-formatting": > > > > git push --delete origin python-formatting > > That did the job, thank you!

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Sun, 1 Dec 2024, Alexander Monakov wrote: > You have to use the name of the branch in the remote repo, > "python-formatting": > > git push --delete origin python-formatting That did the job, thank you! On Sun, 1 Dec 2024, Mark Wielaard wrote: > I believe the correct invocation is: > > $ g

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

Hi Gerald, On Sun, Dec 01, 2024 at 07:26:45PM +0100, Gerald Pfeifer wrote: > On Fri, 23 Aug 2024, Eric Gallager wrote: > >>> The branch, python-formatting has been created > >>> at e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1 (commit) > >> Hmm, are you intentionally creating a branch for the

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Sun, 1 Dec 2024, Gerald Pfeifer wrote: > I tried to delete it via > > # git push origin --delete remotes/origin/python-formatting > > alas just get > > error: unable to delete 'remotes/origin/python-formatting': remote ref does > not exist > > Any idea how to drop that branch again f

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Fri, 23 Aug 2024, Eric Gallager wrote: >>> The branch, python-formatting has been created >>> at e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1 (commit) >> Hmm, are you intentionally creating a branch for the wwwdocs repository >> (i.e., our web pages)? I don't recall us having used one befor

Re: [CAUTION - External Sender] Re: gcc relies on RISC-V vcompress instruction undefined behaviour

Hi Richard, > Please file a bugreport so this issue doesn't get lost. I was struggling to reproduce it on a recent toolchain, but I managed to take one of the gcc test cases and recreate it I think. I submitted https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117383 Thanks, Anton

Re: [gcc-13.3.0] dlopen() crash issue

On Thu, 31 Oct 2024 at 12:12, quic_zijuhu via Gcc wrote: > > i am not sure if this is the good way to report gcc issue. (^^) Please see https://gcc.gnu.org/bugs (or the "Bugs" section of the sidebar on the https://gcc.gnu.org homepage).

Re: gcc relies on RISC-V vcompress instruction undefined behaviour

On Thu, Oct 31, 2024 at 3:55 AM Anton Blanchard via Gcc wrote: > > Hi, > > I think gcc is relying on undefined behaviour with the vcompress instruction. > Unfortunately my test case isn't reproducing on mainline, but gcc looks to > use the fields between the last mask selected field and vl while s

Re: gcc relies on RISC-V vcompress instruction undefined behaviour

> Hi, > > I think gcc is relying on undefined behaviour with the vcompress instruction. > Unfortunately my test case isn't reproducing on mainline, but gcc looks to > use the fields between the last mask selected field and vl while setting > tail agnostic. > > This thread explains how vcompress is

Re: GCC devroom at FOSDEM 2025?

On Tue, 01 Oct 2024 11:48:34 +0200 Thomas Schwinge wrote: > I need two, three people as co-organizers Happy to help, Thomas. Let me know what to do. --jkl

Re: GCC devroom at FOSDEM 2025?

Hi Thomas. > FOSDEM have recently posted the "FOSDEM 2025 call for devrooms", > . > Given the great success of last year's GCC devroom: > , I'd like to apply again, > for a GCC devroom (and relate

RE: GCC nvptx-none Target Testing (was: New page "nvptx" in the GCC wiki to document --target=nvptx-none configurations)

ations: <https://gcc.gnu.org/wiki/nvptx>. > > (I've revised that one -- it's been a few years... -- and in particular > then) I've added more details re "GCC nvptx-none Target Testing": > <https://gcc.gnu.org/wiki/nvptx#GCC_nvptx-none_Target_Testing&

Re: GCC Doxygen documentation

On Mon, 2024-09-23 at 15:45 -0700, Bryon Quackenbush via Gcc wrote: > Greetings all, > >    I am just starting the fun process of getting familiar with the > GCC > compiler and all it's various components (I'm starting out with > LIBCPP, > since that seems relatively small and simple).. Welcome!

Re: gcc-15-20240915 is now available

On 2024-09-17 01:17, Jonathan Wakely via Gcc wrote: On Mon, 16 Sept 2024, 23:40 Alain Mosnier, wrote: On 2024-09-16 23:54, Alain Mosnier wrote: On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote: When a particular snapshot is ready for public consumption the LATEST-15 link is update

Re: gcc-15-20240915 is now available

On Mon, 16 Sept 2024, 23:40 Alain Mosnier, wrote: > On 2024-09-16 23:54, Alain Mosnier wrote: > > On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote: > > > > > When a particular snapshot is ready for public consumption the > > LATEST-15 > > > link is updated > > > > I'm new here. Where do I

Re: gcc-15-20240915 is now available

On 2024-09-16 23:54, Alain Mosnier wrote: On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote: > When a particular snapshot is ready for public consumption the LATEST-15 > link is updated I'm new here. Where do I find the LATEST-15 link? Can I "safely" use the snapshot after the email I

Re: gcc-15-20240915 is now available

On Sun Sep 15 22:38:20 GMT 2024, GCC Administrator wrote: > When a particular snapshot is ready for public consumption the LATEST-15 > link is updated I'm new here. Where do I find the LATEST-15 link? Can I "safely" use the snapshot after the email I am replying to has been sent? Thanks in ad

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Thu, Aug 22, 2024 at 1:27 PM Gerald Pfeifer wrote: > > On Mon, 19 Aug 2024, Eric Gallager via Gcc-cvs-wwwdocs wrote: > > This is an automated email from the git hooks/post-receive script. It was > > generated because a ref change was pushed to the repository containing > > the project "gcc-wwwd

Re: gcc-wwwdocs branch python-formatting created. e1e17c97a8ae35cfb6b2f7428fb52b05f82450d1

On Mon, 19 Aug 2024, Eric Gallager via Gcc-cvs-wwwdocs wrote: > This is an automated email from the git hooks/post-receive script. It was > generated because a ref change was pushed to the repository containing > the project "gcc-wwwdocs". > > The branch, python-formatting has been created >

Re: GCC Quad-Precision Math Library Manual: Errors

On Mon, 19 Aug 2024, 22:27 FX Coudert via Gcc, wrote: > Hi Peter, > > You are right, thanks for reporting these issues in the libquadmath > documentation. I am CC’ing the GCC mailing-list. Does the following patch > seem right? > > diff --git a/libquadmath/libquadmath.texi b/libquadmath/libquadma

Re: GCC Quad-Precision Math Library Manual: Errors

Hi Peter, You are right, thanks for reporting these issues in the libquadmath documentation. I am CC’ing the GCC mailing-list. Does the following patch seem right? diff --git a/libquadmath/libquadmath.texi b/libquadmath/libquadmath.texi index dc2a9ff374b..ce4accf6421 100644 --- a/libquadmath/li

RE: gcc-regression script build fail info

> -Original Message- > From: Sam James > Sent: Thursday, August 15, 2024 6:30 AM > To: Jiang, Haochen > Cc: gcc-regress...@gcc.gnu.org; gcc-testresu...@gcc.gnu.org; > gcc@gcc.gnu.org > Subject: Re: gcc-regression script build fail info > > "Jiang, Haoche

Re: gcc-regression script build fail info

ng, Haochen >> Sent: Thursday, July 18, 2024 3:57 PM >> To: 'Sam James' >> Cc: 'gcc-regress...@gcc.gnu.org' ; 'gcc- >> testresu...@gcc.gnu.org' ; 'gcc@gcc.gnu.org' >> >> Subject: RE: gcc-regression script build fail info >

RE: gcc-regression script build fail info

July 18, 2024 3:57 PM > To: 'Sam James' > Cc: 'gcc-regress...@gcc.gnu.org' ; 'gcc- > testresu...@gcc.gnu.org' ; 'gcc@gcc.gnu.org' > > Subject: RE: gcc-regression script build fail info > > > > > -Original Message- &

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

On Mon, Jul 29, 2024 at 4:34 AM Richard Biener wrote: > On Sun, Jul 28, 2024 at 11:46 PM Jason Merrill via Gcc > wrote: > > > > Since the RC I've fixed a few 14/15 C++ regressions with extremely safe > > patches, and wonder what you think about pushing them to the branch at > this > > point: > >

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

On Sun, Jul 28, 2024 at 11:46 PM Jason Merrill via Gcc wrote: > > Since the RC I've fixed a few 14/15 C++ regressions with extremely safe > patches, and wonder what you think about pushing them to the branch at this > point: > > 115583, 115986, 115561 > > Sorry these came so late. Those are all f

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

Since the RC I've fixed a few 14/15 C++ regressions with extremely safe patches, and wonder what you think about pushing them to the branch at this point: 115583, 115986, 115561 Sorry these came so late. Jason On Tue, Jul 23, 2024 at 8:51 AM Jakub Jelinek via Gcc wrote: > The first release ca

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

On 7/23/24 7:50 AM, Jakub Jelinek via Gcc wrote: The first release candidate for GCC 14.2 is available from https://gcc.gnu.org/pub/gcc/snapshots/14.2.0-RC-20240723/ ftp://gcc.gnu.org/pub/gcc/snapshots/14.2.0-RC-20240723/ and shortly its mirrors. It has been generated from git commit r14-1

Re: GCC 11.5 Released

please unsubscribe me, thanks Op vr 19 jul 2024 om 08:40 schreef Richard Biener via gcc-announce < gcc-annou...@gcc.gnu.org>: > The GNU Compiler Collection version 11.5 has been released. > > GCC 11.5 is a bug-fix release from the GCC 11 branch > containing important fixes for regressions and ser

Re: GCC 11.5 Released

Unsubscribe me please, Thanks Sent from my iPhone > On 19 Jul 2024, at 07:37, Richard Biener via gcc-announce > wrote: > > The GNU Compiler Collection version 11.5 has been released. > > GCC 11.5 is a bug-fix release from the GCC 11 branch > containing important fixes for regressions and se

RE: gcc-regression script build fail info

> -Original Message- > From: Jiang, Haochen > Sent: Thursday, July 18, 2024 3:46 PM > To: 'Sam James' > Cc: 'gcc-regress...@gcc.gnu.org' ; 'gcc- > testresu...@gcc.gnu.org' ; gcc@gcc.gnu.org > Subject: gcc-regression script build fail info > > > > For future reports, would it be possibl

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

> Am 15.07.2024 um 20:07 schrieb William Seurer via Gcc : > > On 7/12/24 7:47 AM, 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

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

On 7/12/24 7:47 AM, 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 so far bootstrapped and teste

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: GCC 14.1.1 Status Report (2024-07-11)

On Sun, Jul 14, 2024 at 08:07:02PM +0800, LIU Hao via Gcc wrote: > 在 2024-07-11 15:56, Jakub Jelinek via Gcc 写道: > > Status > > == > > > > The gcc-14 branch is open for regression and documentation fixes. > > > > It's time to plan for a GCC 14.2 release which should follow > > roughly two to

Re: GCC 14.1.1 Status Report (2024-07-11)

在 2024-07-11 15:56, Jakub Jelinek via Gcc 写道: Status == The gcc-14 branch is open for regression and documentation fixes. It's time to plan for a GCC 14.2 release which should follow roughly two to three months after the .1 release. The plan is to do a release candidate for GCC 14.2 on Tue

Re: GCC Download Issue

On Fri, 5 Jul 2024 at 10:49, Dinesh M via Gcc wrote: > > Hi Gcc Team, > > I am trying to download gcc compiler but didn't download the compiler Please note this quyestion belongs on the gcc-help list, not the gcc list. Why didn't you download it? What did you try? What didn't work? > please giv

Re: gcc git locked out for hours second day in a row

Hello, Le 12/06/2024 à 16:57, Jakub Jelinek a écrit : On Wed, Jun 12, 2024 at 04:53:38PM +0200, Mikael Morin wrote: Perhaps you could create a mirror version of the repo and do some experiments locally on that to identify where the bottle-neck is coming from? Not sure where to start for that

Re: gcc 12.4 release archive?

On Sun, Jun 23, 2024 at 12:02 AM Jonathan Wakely via Gcc wrote: > > On Sat, 22 Jun 2024, 20:41 Liviu Ionescu, wrote: > > > > > > > > On 22 Jun 2024, at 22:02, Andrew Pinski wrote: > > > > > >> GCC 12.4 was released two days ago, but I could not yet find the > > release archive at https://ftp.gnu

Re: gcc 12.4 release archive?

On Sat, 22 Jun 2024, 20:41 Liviu Ionescu, wrote: > > > > On 22 Jun 2024, at 22:02, Andrew Pinski wrote: > > > >> GCC 12.4 was released two days ago, but I could not yet find the > release archive at https://ftp.gnu.org/gnu/gcc/. > >> > >> Could you upload it? > > > > It is located at https://gcc

Re: gcc 12.4 release archive?

> On 22 Jun 2024, at 22:02, Andrew Pinski wrote: > >> GCC 12.4 was released two days ago, but I could not yet find the release >> archive at https://ftp.gnu.org/gnu/gcc/. >> >> Could you upload it? > > It is located at https://gcc.gnu.org/ftp/gcc/releases/gcc-12.4.0/ . Ok, just that this u

Re: gcc 12.4 release archive?

On Sat, Jun 22, 2024 at 3:19 AM Liviu Ionescu wrote: > > Hi, > > GCC 12.4 was released two days ago, but I could not yet find the release > archive at https://ftp.gnu.org/gnu/gcc/. > > Could you upload it? It is located at https://gcc.gnu.org/ftp/gcc/releases/gcc-12.4.0/ . Looks like it was no

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

On Mon, 17 Jun 2024 at 07:17, Richard Biener wrote: > > On Fri, 14 Jun 2024, Jonathan Wakely wrote: > > > On Thu, 13 Jun 2024 at 09:14, Richard Biener via Gcc > > wrote: > > > > > > > > > The first release candidate for GCC 12.4 is available from > > > > > > https://gcc.gnu.org/pub/gcc/snapshots

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

On Fri, 14 Jun 2024, Jonathan Wakely wrote: > On Thu, 13 Jun 2024 at 09:14, 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 generate

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

On Thu, 13 Jun 2024 at 09:14, 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 have so

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

> 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

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

On 6/13/24 3:13 AM, 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 have so far bootstrapped and tes

Re: gcc git locked out for hours second day in a row

On Wed, 12 Jun 2024 at 14:23, Mikael Morin wrote: > > Le 12/06/2024 à 14:58, Jonathan Wakely a écrit : > > On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc wrote: > >> > >> Le 12/06/2024 à 13:48, Jakub Jelinek a écrit : > >>> Hi! > >>> > >>> Yesterday the gcc git repository was locked for 3 hou

Re: gcc git locked out for hours second day in a row

On Wed, Jun 12, 2024 at 04:53:38PM +0200, Mikael Morin wrote: > > Perhaps you could create a mirror version of the repo and do some > > experiments locally on that to identify where the bottle-neck is coming > > from? > > > Not sure where to start for that.Are the hooks published somewhere? Yes

Re: gcc git locked out for hours second day in a row

Le 12/06/2024 à 16:34, Richard Earnshaw (lists) a écrit : On 12/06/2024 14:23, Mikael Morin via Gcc wrote: Le 12/06/2024 à 14:58, Jonathan Wakely a écrit : On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc wrote: Le 12/06/2024 à 13:48, Jakub Jelinek a écrit : Hi! Yesterday the gcc git rep

Re: gcc git locked out for hours second day in a row

On 12/06/2024 14:23, Mikael Morin via Gcc wrote: > Le 12/06/2024 à 14:58, Jonathan Wakely a écrit : >> On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc wrote: >>> >>> Le 12/06/2024 à 13:48, Jakub Jelinek a écrit : Hi! Yesterday the gcc git repository was locked for 3 hours lo

Re: gcc git locked out for hours second day in a row

Le 12/06/2024 à 14:58, Jonathan Wakely a écrit : On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc wrote: Le 12/06/2024 à 13:48, Jakub Jelinek a écrit : Hi! Yesterday the gcc git repository was locked for 3 hours locked by user mikael at 2024-06-11 13:27:44.301067 (pid = 974167) 78:06 pytho

Re: gcc git locked out for hours second day in a row

On Wed, 12 Jun 2024 at 13:57, Mikael Morin via Gcc wrote: > > Le 12/06/2024 à 13:48, Jakub Jelinek a écrit : > > Hi! > > > > Yesterday the gcc git repository was locked for 3 hours > > locked by user mikael at 2024-06-11 13:27:44.301067 (pid = 974167) > > 78:06 python hooks/update.py > > refs/use

Re: gcc git locked out for hours second day in a row

Le 12/06/2024 à 14:14, Mark Wielaard a écrit : Hi, On Wed, 2024-06-12 at 13:48 +0200, Jakub Jelinek via Gcc wrote: Yesterday the gcc git repository was locked for 3 hours locked by user mikael at 2024-06-11 13:27:44.301067 (pid = 974167) 78:06 python hooks/update.py refs/users/mikael/tags/fortr

Re: gcc git locked out for hours second day in a row

Le 12/06/2024 à 13:48, Jakub Jelinek a écrit : Hi! Yesterday the gcc git repository was locked for 3 hours locked by user mikael at 2024-06-11 13:27:44.301067 (pid = 974167) 78:06 python hooks/update.py refs/users/mikael/tags/fortran-dev_merges/r10-1545

Re: gcc git locked out for hours second day in a row

Hi, On Wed, 2024-06-12 at 13:48 +0200, Jakub Jelinek via Gcc wrote: > Yesterday the gcc git repository was locked for 3 hours > locked by user mikael at 2024-06-11 13:27:44.301067 (pid = 974167) > 78:06 python hooks/update.py > refs/users/mikael/tags/fortran-dev_merges/r10-1545 > 000

Re: GCC trouble in dump_printf_loc

On Mon, Jun 3, 2024 at 2:54 AM weizhe wang via Gcc wrote: > > Hi Guys, > > > > I got some issues in debugging GCC. > > I want to use dump_printf_loc to dump some debug message in GCC. I find > the fopt-info-all option which can enable some dump_printf_loc calls. > > But some dump_p

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

On 5/14/24 11:31 AM, 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 from git commit r1

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

> 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

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

On Tue, May 14, 2024 at 06:31:19PM +0200, Jakub Jelinek via Gcc wrote: > If all goes well, we'd like to release 13.3 on Thursday, May 21st. Tuesday, May 21st. Sorry for the pasto. Jakub

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: GCC 14.1 Release Candidate available from gcc.gnu.org

Bootstrapping the following configuration (with LRA enabled) looks good for ia64, too: ``` CFLAGS="-O2 -fPIC" \ CXXFLAGS="-O2 -fPIC" \ ../configure --prefix=/usr \ --enable-obsolete \ --libdir=/usr/lib \ --mandir=/usr/man \ --infodir=/usr/info \ --enable-shared \ --enable-bootstrap \ --enable-lan

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

I bootstrapped and tested on powepc64 8 and 9 BE and 8, 9, and 10 LE and it looks good. On 4/30/24 5:33 AM, 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/

Re: GCC testing on FreeBSD

Hi Lorenzo, > I totally agree with you: upstreaming patches is important! It is not > only for the upstream project itself, but for the target as well: having > patches sitting in a ports collection also requires more maintainance, > they require to be kept up to date with the upstream progresses.

Re: GCC testing on FreeBSD

On Sunday, April 28th, 2024 at 19:19, Rainer Orth wrote: > > > Hi Lorenzo, > > > On Sunday, April 28th, 2024 at 12:24, Gerald Pfeifer ger...@pfeifer.com > > wrote: > > > > > On Fri, 26 Apr 2024, Jonathan Wakely wrote: > > > > > > > How are you testing on FreeBSD? > > > > > > > > When I bu

Re: GCC testing on FreeBSD

Hi Lorenzo, > On Sunday, April 28th, 2024 at 12:24, Gerald Pfeifer > wrote: > >> On Fri, 26 Apr 2024, Jonathan Wakely wrote: >> >> > How are you testing on FreeBSD? >> > >> > When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++ >> > testsuite it fails due to lots of these errors

Re: GCC testing on FreeBSD

On Sun, 28 Apr 2024, 11:24 Gerald Pfeifer, wrote: > Hi Jonathan, > > On Fri, 26 Apr 2024, Jonathan Wakely wrote: > > How are you testing on FreeBSD? > > > > When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++ > > testsuite it fails due to lots of these errors: > > > > Excess error

Re: GCC testing on FreeBSD

On Sunday, April 28th, 2024 at 12:24, Gerald Pfeifer wrote: > On Fri, 26 Apr 2024, Jonathan Wakely wrote: > > > How are you testing on FreeBSD? > > > > When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++ > > testsuite it fails due to lots of these errors: > > > > Excess errors:

Re: GCC testing on FreeBSD

Hi Gerald, > On Fri, 26 Apr 2024, Jonathan Wakely wrote: >> How are you testing on FreeBSD? >> >> When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++ >> testsuite it fails due to lots of these errors: >> >> Excess errors: >> /usr/local/bin/ld: /tmp//ccev946q.o: relocation R_X86_6

Re: GCC testing on FreeBSD

Hi Jonathan, On Fri, 26 Apr 2024, Jonathan Wakely wrote: > How are you testing on FreeBSD? > > When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++ > testsuite it fails due to lots of these errors: > > Excess errors: > /usr/local/bin/ld: /tmp//ccev946q.o: relocation R_X86_64_32 ag

Re: gcc 3.2.3 x64 negative indexes

Problem solved. I didn't have this: #define SIZE_TYPE (TARGET_64BIT ? "long unsigned int" : "unsigned int") because I wasn't including x86_64.h. This is the first time I have attempted to go to 64-bit pointers so I wasn't aware this even existed. So here it is doing Win64 ABI: D:\devel\gcc\gc

Re: gcc 3.2.3 x64 negative indexes

(replying to Joe Monk) > It appears that this is not an issue that this version of GCC is > architected to be able to solve. > The first 64-bit PC processor, the AMD opteron series, was launched on > April 22, 2003. > GCC 3.2.3 was released on April 25, 2003. Jakub has already shown correct x64

Re: gcc 3.2.3 x64 negative indexes

It appears that this is not an issue that this version of GCC is architected to be able to solve. The first 64-bit PC processor, the AMD opteron series, was launched on April 22, 2003. GCC 3.2.3 was released on April 25, 2003. "*Opteron* is AMD

Re: gcc 3.2.3 x64 negative indexes

I have it down to a deliberate conversion from signed to unsigned: temp.txt: bbb piss ccc 32 32 temp.txt: bbb piss ccc2 0 1 temp.txt: bbb piss ddd -2 temp.txt: bbb - in convert temp.txt: bbb - converting to integer temp.txt: bbb y stage1 temp.txt: bbb y stage2 temp.txt: bbb y outprec thing, inprec

Re: gcc 3.2.3 x64 negative indexes

Oh - I switched to -2 to make debugging easier: D:\devel\gcc\gcc>type foo.c int foo(char *in) { return in[-2]; } D:\devel\gcc\gcc> Note that my flavor of gcc 3.2.3 can be found in gcc-stage*.zip in custom.zip at http://pdos.org On Sat, 10 Feb 2024 at 05:34, Paul Edwards wrote: > On Wed, 7

  1   2   3   4   5   6   7   8   9   10   >