Fwd: [GSoC] Application RFC + Question - GENERIC dump

Forgot to CC the mailing list - mea culpa. -- Forwarded message - From: Thor Preimesberger Date: Tue, Apr 2, 2024 at 5:57 PM Subject: Re: [GSoC] Application RFC + Question - GENERIC dump To: Richard Biener Thanks for the quick feedback, especially on such short notice - I'll

Re: [GSoC] Application RFC + Question - GENERIC dump

On Tue, Apr 2, 2024 at 11:14 AM Thor Preimesberger via Gcc wrote: > > Forgot to CC the mailing list - mea culpa. > > -- Forwarded message - > From: Thor Preimesberger > Date: Tue, Apr 2, 2024 at 5:57 PM > Subject: Re: [GSoC] Application RFC + Question - GENERIC dump > To: Richard

Re: [GSoC] Interest in applying

Hello, On Sun, Mar 31 2024, tmpod via Gcc wrote: > Hello, > > I am a Computer Science student, currently taking a Master's degree in > > > Portugal's top university. I have

Re: [GSoC] Application RFC + Question - GENERIC dump

On Mon, Apr 1, 2024 at 6:23 PM Thor Preimesberger via Gcc wrote: > > Hey all, > > I'm joining the group of people submitting their GSoC applications > over the holiday. I'm interested in the "Implement structured dumping > of GENERIC" project idea, and the application I've written is below.

Re: GSoC Timeline Review

On Sat, 2024-03-30 at 13:54 +0200, Nada Elsayed wrote: > I think that I didn't fully understand the project, so I read more > and > updated the Timeline Suggestion. Hi Nada I'm very sorry for not responding sooner; I've been dealing with an difficult issue that's arisen outside of my computer

Re: GSoC Timeline Review

Hello, On Sat, Mar 30 2024, Nada Elsayed via Gcc wrote: > I think that I didn't fully understand the project, so I read more and > updated the Timeline Suggestion. Sorry that we were for not being able to respond sooner, Easter got into way in an unfortunate way. I do not know much about Cython

Re: GSoC Timeline Review

On Tue, 2024-04-02 at 10:06 -0400, David Malcolm wrote: > What timezone are you in?  (I'm in EDT, UTC+4) Sorry, that should be UTC-4 (on the east coast of the US) Dave

Re: Sourceware mitigating and preventing the next xz-backdoor

On 4/1/24 09:06, Mark Wielaard wrote: A big thanks to everybody working this long Easter weekend who helped analyze the xz-backdoor and making sure the impact on Sourceware and the hosted projects was minimal. This email isn't about the xz-backdoor itself. Do see Sam James FAQ

Re: Sourceware mitigating and preventing the next xz-backdoor

> On Apr 2, 2024, at 4:03 PM, Paul Eggert wrote: > > On 4/2/24 12:54, Sandra Loosemore wrote: >> Do we to harden our process, too, to require all patches to be signed off by >> someone else before committing? > > It's easy for an attacker to arrange to have "someone else" in cahoots. > >

Re: Sourceware mitigating and preventing the next xz-backdoor

On Tue, Apr 2, 2024 at 1:21 PM Paul Koning via Gcc wrote: > > Would it help to require (rather than just recommend) "don't use root except > for the actual 'install' step" ? Seems reasonable, but note that it wouldn't make any difference to this attack. The liblzma library was modified to

Re: AutoFDO tools for GCC

Thanks for initiating this discussion Eugene. For a little bit more context on the motivation -- Meta has developed a new type of AutoFDO which is committed upstream in LLVM and we want to unify our tooling with this approach. > I do wonder how much common code there is > between the LLVM and the

Re: Sourceware mitigating and preventing the next xz-backdoor

On 4/2/24 12:54, Sandra Loosemore wrote: Do we to harden our process, too, to require all patches to be signed off by someone else before committing? It's easy for an attacker to arrange to have "someone else" in cahoots. Although signoffs can indeed help catch inadvertent mistakes, they're

Re: Sourceware mitigating and preventing the next xz-backdoor

On 4/2/24 16:54, Sandra Loosemore wrote: On 4/1/24 09:06, Mark Wielaard wrote: A big thanks to everybody working this long Easter weekend who helped analyze the xz-backdoor and making sure the impact on Sourceware and the hosted projects was minimal. This email isn't about the xz-backdoor

Re: Sourceware mitigating and preventing the next xz-backdoor

On Tue, Apr 2, 2024 at 6:09 PM Guinevere Larsen via Gdb wrote: > [...] > What likely happened for the maintainer who acted in bad faith was that > they entered the project with bad faith intent from the start - seeing > as they were only involved with the project for 2 years, and there was > much

Re: Sourceware mitigating and preventing the next xz-backdoor

> On Apr 2, 2024, at 6:08 PM, Guinevere Larsen wrote: > > On 4/2/24 16:54, Sandra Loosemore wrote: >> On 4/1/24 09:06, Mark Wielaard wrote: >>> A big thanks to everybody working this long Easter weekend who helped >>> analyze the xz-backdoor and making sure the impact on Sourceware and >>>

Re: Sourceware mitigating and preventing the next xz-backdoor

On Tue, Apr 2, 2024 at 7:35 PM Paul Koning via Gdb wrote: > [...] > > I agree that GDB, and for that matter other projects with significant numbers > of contributors, are not nearly as likely to be vulnerable to this sort of > attack. But I worry that xz may not be the only project that's

[Bug c/114554] In O2-3 optimization, this code runs in an infinite loop.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114554 --- Comment #2 from Andrew Pinski --- Plus I get the following warnings at -O2: In function 'wyrand', inlined from 'main' at :84:5: :76:7: warning: iteration 2 invokes undefined behavior [-Waggressive-loop-optimizations] 76 | *p1 +=

Results for 13.2.1 20240402 [releases/gcc-13 r13-8554-g289bf7b1fa] (GCC) testsuite on powerpc64le-unknown-linux-gnu

htly/build-gcc-13/gcc/xgcc version 13.2.1 20240402 [releases/gcc-13 r13-8554-g289bf7b1fa] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O1 execution

Re: [PATCH] LoongArch: Remove unused code and add sign/zero-extend for vpickve2gr.d

We recently discovered an issue with the sign/zero extension behavior of |[x]vpickve2gr.|The QI , HI and SI are extended to SI instead of DI, which may lead to the generation of additional sign extension instructions. We have decided to fix this issue in the next version. I will upload a new

[Bug c/114554] New: In O2-3 optimization, this code runs in an infinite loop.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114554 Bug ID: 114554 Summary: In O2-3 optimization, this code runs in an infinite loop. Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug c/114554] In O2-3 optimization, this code runs in an infinite loop.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114554 --- Comment #4 from nmodnation n --- I apologize for taking up your time because of my mistake. I will be careful from next time. thank you 2024년 4월 2일 (화) 오후 3:35, pinskia at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org>님이 작성: >

☠ Buildbot (Sourceware): gcc-autoregen - failed 'git diff ...' (failure) (master)

A new failure has been detected on builder gcc-autoregen while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#/builders/269/builds/4100 Build state: failed 'git diff ...' (failure) Revision: b253b4695ddac43301bb572895095b9569165ff4 Worker: bb2-1 Build

[Bug rtl-optimization/85426] ICE in patch_jump_insn, at cfgrtl.c:1271

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85426 Andrew Pinski changed: What|Removed |Added Last reconfirmed||2024-04-02 Known to fail|

[gcc r14-9742] LoongArch: Add support for TLS descriptors.

https://gcc.gnu.org/g:b253b4695ddac43301bb572895095b9569165ff4 commit r14-9742-gb253b4695ddac43301bb572895095b9569165ff4 Author: mengqinggang Date: Tue Apr 2 09:57:20 2024 +0800 LoongArch: Add support for TLS descriptors. Add support for TLS descriptors on normal code model and

Re: [PATCH v2] rs6000: Stackoverflow in optimized code on PPC [PR100799]

Hi! on 2024/3/24 02:37, Ajit Agarwal wrote: > > > On 23/03/24 9:33 pm, Peter Bergner wrote: >> On 3/23/24 4:33 AM, Ajit Agarwal wrote: > - else if (align_words < GP_ARG_NUM_REG) > + else if (align_words < GP_ARG_NUM_REG > +|| (cum->hidden_string_length > +

[Bug c/114554] In O2-3 optimization, this code runs in an infinite loop.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114554 Andrew Pinski changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED

[Bug c/114554] In O2-3 optimization, this code runs in an infinite loop.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114554 --- Comment #3 from Andrew Pinski --- Also didn't you read https://gcc.gnu.org/bugs/ or even what is mentioned on the bug entry web page? https://gcc.gnu.org/bugs/ says: Before reporting that GCC compiles your code incorrectly, compile it with

Re: [pushed][PATCH v5] LoongArch: Add support for TLS descriptors

Pushed to r14-9742. Rebase to the latest, and modify invoke.texi to add a description of the TLS DESC compilation option. 在 2024/3/19 上午9:54, mengqinggang 写道: Add support for TLS descriptors on normal code model and extreme code model. Normal code model instruction sequence:

[Bug c/31128] __builtin_stack_restore/__builtin_stack_save should not be exposed to the user

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31128 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

Re: [PATCH] Prettify output of debug_dwarf_die

On Thu, Mar 28, 2024 at 8:35 PM Tom Tromey wrote: > > When debugging gcc, I tried calling debug_dwarf_die and I saw this > output: > > DW_AT_location: location descriptor: > (0x7fffe9c2e870) DW_OP_dup 0, 0 > (0x7fffe9c2e8c0) DW_OP_bra location descriptor (0x7fffe9c2e640) > ,

[PATCH v1] LoongArch: Set default alignment for functions jumps and loops [PR112919].

Xi Ruoyao set the alignment rules under LA464 in commit r14-1839, but the macro ASM_OUTPUT_ALIGN_WITH_NOP was removed in R14-4674, which affected the alignment rules. So I set different aligns on LA464 and LA664 again to test the performance of spec2006, and modify the alignment based on the test

Re: [pushed][PATCH] LoongArch: Fix missing plugin header

Pushed to r14-9743. 在 2024/4/2 上午9:20, Yang Yujie 写道: gcc/ChangeLog: * config/loongarch/t-loongarch: Add loongarch-def-arrays.h to OPTION_H_EXTRA. --- gcc/config/loongarch/t-loongarch | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[PATCH] Fix up duplicated words mostly in comments, part 1

Hi! Like in r12-7519-g027e30414492d50feb2854aff38227b14300dc4b, I've done git grep -v 'long long\|optab optab\|template template\|double double' | grep ' \([a-zA-Z]\+\) \1 ' This is just part of the changes, mostly for non-gcc directories. I'll try to get to the rest soon. Obviously, the above

[PATCH v2] RISC-V: Refine the condition for add additional vars in RVV cost model

The adjacent_dr_p is sufficient and unnecessary condition for contiguous access. So unnecessary live-ranges are added and result in smaller LMUL. This patch uses MEMORY_ACCESS_TYPE as condition and constrains segment load/store. Tested on RV64 and no regression. PR target/114506

Results for 14.0.1 20240402 (experimental) [master r14-9741-g6f9ba3ea55477c] (GCC) testsuite on aarch64-suse-linux-gnu

# of unexpected failures2 /opt/gcc/gcc-20240402/Build/./gcc/gccgo version 14.0.1 20240402 (experimental) [master r14-9741-g6f9ba3ea55477c] (GCC) === libgomp tests === Running target unix/-mabi=lp64 === libgomp Summary === # of expected passes16260

[Bug c/114558] New: GCC 13.2.1 encountered a segmentation fault error when compiling PyTorch.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114558 Bug ID: 114558 Summary: GCC 13.2.1 encountered a segmentation fault error when compiling PyTorch. Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity:

Re: [PATCH] Fix up duplicated words mostly in comments, part 1

On Tue, 2 Apr 2024 at 08:47, Jakub Jelinek wrote: > > Hi! > > Like in r12-7519-g027e30414492d50feb2854aff38227b14300dc4b, I've done > git grep -v 'long long\|optab optab\|template template\|double double' | grep > ' \([a-zA-Z]\+\) \1 ' > > This is just part of the changes, mostly for non-gcc

[PATCH][wwwdocs] changes.html changes for AArch64 for GCC 14.1

Hi all, Here's a writeup of the AArch64 changes to highlight in GCC 14.1. If there's something you'd like to highlight feel free to comment or add a patch yourself. I don't expect the list to be exhaustive. It's been a busy release for AArch64! Thanks, Kyrill gcc-14-aarch64-wwwdocs.patch

gcc-wwwdocs branch master updated. 501aef9bacc3842d0b7d022a4333c9d71d419d4d

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, master has been updated via 501aef9bacc3842d0b7d022a4333c9d71d419d4d (commit) from

[Bug c++/114562] New: ICE when trying to bind rvalue reference to lvalue with comma operator and forwarding reference to pointer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114562 Bug ID: 114562 Summary: ICE when trying to bind rvalue reference to lvalue with comma operator and forwarding reference to pointer Product: gcc Version: 14.0

[Bug tree-optimization/114557] ehcleanup cleanup_empty_eh_merge_phis eats a lot of memory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114557 --- Comment #2 from Richard Biener --- The free_phinodes buckets itself could better use the ->next chain of the gimple stmts rather than a (re-allocated) GC vector. Given the current bucket structure a single chain for the 4-argument case

Results for 12.3.1 20240402 [remotes/origin/releases/gcc-12 r12-10304-g351e923897] (GCC) testsuite on powerpc64le-unknown-linux-gnu

2078 # of unexpected failures170 # of unexpected successes 14 # of expected failures 1468 # of unsupported tests 3885 /home/gccbuild/build/nightly/build-gcc-12/gcc/xgcc version 12.3.1 20240402 [remotes/origin/releases/gcc-12 r12-10304-g351e923897] (GCC)

[pushed] testsuite, Darwin: Update bad-mapper-1 after libiberty changes.

Tested on i686-darwin9, x86_64-darwin17, 21, 23, and on x86_64 and powerpc64 linux gnu, pushed to trunk, thanks, Iain --- 8< --- A recent change to libiberty has improved the process spawning on older Darwin platforms. This patch updates the expected test output after the changes.

[gcc r14-9747] testsuite, Darwin: Allow for an undefined symbol [PR114036].

https://gcc.gnu.org/g:ad8e34eaa870608e2b07b4e7147e6ef2944bb8b5 commit r14-9747-gad8e34eaa870608e2b07b4e7147e6ef2944bb8b5 Author: Iain Sandoe Date: Sun Mar 31 11:27:53 2024 +0100 testsuite, Darwin: Allow for an undefined symbol [PR114036]. Darwin's linker defaults to requiring all

[PATCH] tree-optimization/114557 - reduce ehcleanup peak memory use

The following reduces peak memory use for the PR114480 testcase at -O1 which is almost exclusively spent by the ehcleanup pass in allocating PHI nodes. The free_phinodes cache we maintain isn't very effective since it has effectively two slots, one for 4 and one for 9 argument PHIs and it is only

[Bug target/114036] Test failure of gcov-14.c on darwin

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114036 --- Comment #4 from GCC Commits --- The master branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:ad8e34eaa870608e2b07b4e7147e6ef2944bb8b5 commit r14-9747-gad8e34eaa870608e2b07b4e7147e6ef2944bb8b5 Author: Iain Sandoe Date:

[Bug testsuite/114034] Failure of tests gcov-dump-{1,2}.C

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114034 --- Comment #3 from GCC Commits --- The master branch has been updated by Iain D Sandoe : https://gcc.gnu.org/g:799a056cf804f433ce0050a5a6bf900f7a01ecb1 commit r14-9748-g799a056cf804f433ce0050a5a6bf900f7a01ecb1 Author: Iain Sandoe Date:

[gcc r14-9748] testsuite: Remove duplicate -lgcov [PR114034]

https://gcc.gnu.org/g:799a056cf804f433ce0050a5a6bf900f7a01ecb1 commit r14-9748-g799a056cf804f433ce0050a5a6bf900f7a01ecb1 Author: Iain Sandoe Date: Sun Mar 31 11:22:58 2024 +0100 testsuite: Remove duplicate -lgcov [PR114034] Duplicate library entries now cause linker warnings with

[gcc r14-9749] jit, Darwin: Implement library exports list.

https://gcc.gnu.org/g:b120e355e59142bd15d6b010461d07236288d843 commit r14-9749-gb120e355e59142bd15d6b010461d07236288d843 Author: Iain Sandoe Date: Sat Jan 13 17:20:47 2024 + jit, Darwin: Implement library exports list. Currently, we have no exports list for libgccjit, which

[Bug middle-end/114552] [13/14 Regression] wrong code at -O1 and above on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114552 Richard Biener changed: What|Removed |Added Version|unknown |14.0 Priority|P3

[Bug c++/114561] Comma operator with forwarding reference to pointer raises invalid lvalue required error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114561 --- Comment #3 from Jonathan Wakely --- Further reduced: void create(void* u) { const void* const& r = ( (void)0, u ); } void test_func() { create(0); } The result of (0, u) is an lvalue of type void* which should then be converted

Results for 14.0.1 20240402 (experimental) [master revision gcc-14-9743-g078f4a958cd] (GCC) testsuite on aarch64-unknown-linux-gnu

=== libgo Summary === # of expected passes196 /home/tcwg-buildslave/workspace/tcwg_gnu_5/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/gcc-gcc.git~master-stage2/./gcc/gccgo version 14.0.1 20240402 (experimental) [master revision gcc-14-9743

[gcc r14-9751] Fix up postboot dependencies [PR106472]

https://gcc.gnu.org/g:9a5e4aade2b847c5262577a1490ce6f3df9a9841 commit r14-9751-g9a5e4aade2b847c5262577a1490ce6f3df9a9841 Author: Jakub Jelinek Date: Tue Apr 2 13:40:27 2024 +0200 Fix up postboot dependencies [PR106472] On Wed, Mar 13, 2024 at 10:13:37AM +0100, Jakub Jelinek

[Bug bootstrap/106472] No rule to make target '../libbacktrace/libbacktrace.la', needed by 'libgo.la'.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472 --- Comment #38 from GCC Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:9a5e4aade2b847c5262577a1490ce6f3df9a9841 commit r14-9751-g9a5e4aade2b847c5262577a1490ce6f3df9a9841 Author: Jakub Jelinek Date:

[Bug tree-optimization/114555] New: ICE: definition in block 14 does not dominate use in block 15 at -O and above with _BitInt() bitfield

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114555 Bug ID: 114555 Summary: ICE: definition in block 14 does not dominate use in block 15 at -O and above with _BitInt() bitfield Product: gcc Version: 14.0 Status:

Results for 14.0.1 20240402 (experimental) [master revision gcc-14-9742-gb253b4695dd] (GCC) testsuite on aarch64-unknown-linux-gnu

rted tests 4689 /home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/aarch64-unknown-linux-gnu/bin/aarch64-unknown-linux-gnu-gcc version 14.0.1 20240402 (experimental) [master revision gcc-14-9742-gb253b4695dd] (GCC) === gfortran tests === Running target

[gcc r14-9743] LoongArch: Fix missing plugin header

https://gcc.gnu.org/g:078f4a958cd2267d5b1dccda838785836ac19b79 commit r14-9743-g078f4a958cd2267d5b1dccda838785836ac19b79 Author: Yang Yujie Date: Tue Apr 2 09:20:32 2024 +0800 LoongArch: Fix missing plugin header gcc/ChangeLog: * config/loongarch/t-loongarch: Add

[Bug rtl-optimization/114522] [14 regression] gcc.target/arm/aes_xor_combine.c scan-assembler-not veor fails after r14-9692-g839bc42772ba7a

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114522 Richard Biener changed: What|Removed |Added Target||arm Priority|P2

[Bug rtl-optimization/114556] New: weird loop unrolling when there's attribute aligned in side the loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114556 Bug ID: 114556 Summary: weird loop unrolling when there's attribute aligned in side the loop Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug modula2/114529] profiledbootstrap fails to build and m2 causes odr violations during build

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114529 --- Comment #2 from Arsen Arsenović --- full build.log also: https://dev.gentoo.org/~arsen/gcc-14.0.1_pre20240331-Werror-odr-build.log.gz

[Bug middle-end/114559] New: After function inlining some optimizations missing

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114559 Bug ID: 114559 Summary: After function inlining some optimizations missing Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal

[Bug c++/114561] New: Comma operator with forwarding reference to pointer raises invalid lvalue required error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114561 Bug ID: 114561 Summary: Comma operator with forwarding reference to pointer raises invalid lvalue required error Product: gcc Version: 14.0 Status: UNCONFIRMED

[Bug gcov-profile/114115] xz-utils segfaults when built with -fprofile-generate (bad interaction between IFUNC and binding?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114115 --- Comment #10 from Sam James --- I'm aware, but there's a minimised test case attached here which shows this is still somewhat of a problem by itself. Either a better diagnostic is needed or to not instrument the resolver.

[Bug c++/114561] Comma operator with forwarding reference to pointer raises invalid lvalue required error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114561 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2024-04-02 See Also|

[Bug c++/57573] [C++1y] bogus "taking address of temporary" error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57573 Jonathan Wakely changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[pushed] Darwin: Correct a version check.

Tested on x86_64-darwin17,21,23, pushed to trunk, thanks, Iain --- 8< --- When the version for dsymutil comes from a clang build, it is of the form NNmm.pp.qq where NN and mm are the major and minor LLVM version components. We need to check for a major version greater than or equal to 7 - so

[pushed] testsuite: Remove duplicate -lgcov [PR114034]

Tested on x86_64, i686 Darwin and x86_64, powerpc64 linux, pushed to trunk as obvious, thanks Iain --- 8< --- Duplicate library entries now cause linker warnings with newer linker versions on Darwin which leads to these tests regressing. The library is already added by the test flags so there

[Bug c++/114549] [11/12/13 Regression] GCC >= 10.1 selects the wrong overload of C++20 reversed operator== function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114549 Richard Biener changed: What|Removed |Added Priority|P3 |P2

[Bug tree-optimization/114551] [14 Regression] wrong code at -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114551 Richard Biener changed: What|Removed |Added Priority|P3 |P1 Version|unknown

[gcc r14-9750] Fix up duplicated words mostly in comments, part 1

https://gcc.gnu.org/g:94792057ad4a81bb10cdd20085c31df3ca59177e commit r14-9750-g94792057ad4a81bb10cdd20085c31df3ca59177e Author: Jakub Jelinek Date: Tue Apr 2 13:39:11 2024 +0200 Fix up duplicated words mostly in comments, part 1 Like in

Re: [PATCH] jit, Darwin: Implement library exports list.

Hi David, > On 25 Jan 2024, at 10:16, Iain Sandoe wrote: > >> On 24 Jan 2024, at 18:31, David Malcolm wrote: >> >> On Tue, 2024-01-16 at 11:10 +, Iain Sandoe wrote: >>> Tested on x86_64, i686 Darwin and x86_64 Linux, >>> OK for trunk? when ? >>> thanks, >>> Iain >> >> Hi Iain, thanks

Re: [PATCH][Backport][GCC10] Fix SSA corruption due to widening_mul opt on conflict across an abnormal edge [PR111407]

On Mon, Apr 1, 2024 at 3:36 PM Qing Zhao wrote: > > This is a bug in tree-ssa-math-opts.c, when applying the widening mul > optimization, the compiler needs to check whether the operand is in a > ABNORMAL PHI, if YES, we should avoid the transformation. > > PR tree-optimization/111407 > >

[PATCH] Fix up postboot dependencies [PR106472]

On Wed, Mar 13, 2024 at 10:13:37AM +0100, Jakub Jelinek wrote: > While the first Makefile.tpl hunk looks obviously ok, the others look > completely wrong to me. > There is nothing special about libgo vs. libbacktrace/libatomic > compared to any other target library which is not bootstrapped vs.

Re: [PATCH v2] rs6000: Stackoverflow in optimized code on PPC [PR100799]

On Tue, Apr 02, 2024 at 02:12:04PM +0800, Kewen.Lin wrote: > The old code for the unused hidden parameter (which was the 9th param) > would > fall thru to the "return NULL_RTX;" which would make the callee assume > there > was a parameter save area allocated. Now

[Bug target/112980] 64-bit powerpc ELFv2 does not allow nops to be generated before function global entry point

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112980 --- Comment #10 from Kewen Lin --- Created attachment 57844 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57844=edit patch changing the current implementation Considering the current implementation is not useful at all for both kernel

[PATCH v2 1/1] [RISC-V] Add support for _Bfloat16

1 At point , BF16 has already been completed "post public review". 2 LLVM has also added support for RISCV BF16 in and . 3 According to the discussion

[PATCH v2 0/1] [RISC-V] Add support for _Bfloat16

Hi all RISC-V folks: This patch completes the support for the bf16 data type in the riscv architecture.On this basis, there will be a series of patches in the future to strengthen support for BF16. It is recommended to first review this patch from the testcases, where detailed explanations have

Results for 14.0.1 20240402 (experimental) [remotes/origin/HEAD r14-9743-g078f4a958c] (GCC) testsuite on powerpc64le-unknown-linux-gnu

an/ieee128-math.f90 -O (test for excess errors) === gcc Summary === # of expected passes179228 # of unexpected failures114 # of unexpected successes 19 # of expected failures 1614 # of unsupported tests 4242 /home/gccbuild/build/

Results for 14.0.1 20240402 (experimental) [remotes/origin/HEAD r14-9743-g078f4a958cd] (GCC) testsuite on powerpc64le-unknown-linux-gnu

cbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240402 (experimental) [remotes/origin/HEAD r14-9743-g078f4a958cd] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test XPASS: gfortran.dg/large_real_

Results for 13.2.1 20240402 [native/releases/gcc-13 r13-8555-g11f37868bb5] (GCC) testsuite on x86_64-pc-linux-gnu

LAST_UPDATED: Tue Apr 2 08:40:04 UTC 2024 (revision r13-8555-g11f37868bb5) Native configuration is x86_64-pc-linux-gnu === gcc tests === Running target unix FAIL: gcc.dg/analyzer/data-model-4.c (test for excess errors) FAIL: gcc.dg/analyzer/torture/conftest-1.c -O0 (test

[Bug middle-end/114563] ggc_internal_alloc is slow

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114563 Richard Biener changed: What|Removed |Added Keywords||compile-time-hog See Also|

Results for 13.2.1 20240402 [releases/gcc-13 r13-8555-g11f37868bb] (GCC) testsuite on powerpc64le-unknown-linux-gnu

ion 13.2.1 20240402 [releases/gcc-13 r13-8555-g11f37868bb] (GCC) === gfortran tests === Running target unix XPASS: gfortran.dg/default_format_2.f90 -O0 execution test XPASS: gfortran.dg/default_format_2.f90 -O1 execution test XPASS: gfortran.dg/default_format_2.f90 -O2

Results for 14.0.1 20240402 (experimental) [master r14-9741-g6f9ba3ea554] (GCC) testsuite on x86_64-pc-linux-gnu

of unsupported tests 3433 === gcc Summary === # of expected passes601565 # of unexpected failures401 # of unexpected successes 59 # of expected failures 4657 # of unsupported tests 10814 /export/project/git/gcc-test-master-intel64/b

Regressions on master at commit r14-9741 vs commit r14-9737 on Linux/x86_64

Regressions on master at commit r14-9741 vs commit r14-9737 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps

[Bug libgcc/111731] [13/14 regression] gcc_assert is hit at libgcc/unwind-dw2-fde.c#L291

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111731 Richard Biener changed: What|Removed |Added Known to work||13.2.1 Known to fail|

[gcc r14-9746] Darwin: Correct a version check.

https://gcc.gnu.org/g:451bb0b9262d2f54173937569a29d7f1ad234e30 commit r14-9746-g451bb0b9262d2f54173937569a29d7f1ad234e30 Author: Iain Sandoe Date: Mon Apr 1 20:47:25 2024 +0100 Darwin: Correct a version check. When the version for dsymutil comes from a clang build, it is of

[Bug libquadmath/114533] libquadmath: printf: fix misaligned access on args

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533 Richard Biener changed: What|Removed |Added Keywords||ABI CC|

[Bug fortran/114535] [13/14 regression] ICE with elemental finalizer

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114535 Richard Biener changed: What|Removed |Added Target Milestone|--- |13.3 Priority|P3

[PATCH] LoongArch: Remove unused code

For machines that satisfy ISA_HAS_LSX && !TARGET_64BIT, we will not support them now and in the future, so this patch removes these unused code. gcc/ChangeLog: * config/loongarch/lasx.md: Remove unused code. * config/loongarch/loongarch-protos.h (loongarch_split_lsx_copy_d):

Regressions on master at commit r14-9738 vs commit r14-9728 on Linux/x86_64

Regressions on master at commit r14-9738 vs commit r14-9728 on Linux/x86_64 New failures: New passes: FAIL: gcc.dg/lto/save-temps c_lto_save-temps_0.o-c_lto_save-temps_0.o link, -O -flto -save-temps FAIL: gcc.dg/torture/convert-dfp-2.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects

Results for 14.0.1 20240401 (experimental) [master r14-9738-gbba118db3f6] (GCC) testsuite on x86_64-pc-linux-gnu

LAST_UPDATED: Mon Apr 1 16:30:07 UTC 2024 (revision r14-9738-gbba118db3f6) Native configuration is x86_64-pc-linux-gnu === gcc tests === Running target unix XPASS: gcc.dg/guality/example.c -O0 execution test XPASS: gcc.dg/guality/example.c -Og -DPREVENT_OPTIMIZATION

[Bug libgcc/111731] [13/14 regression] gcc_assert is hit at libgcc/unwind-dw2-fde.c#L291

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111731 --- Comment #21 from GCC Commits --- The releases/gcc-13 branch has been updated by Thomas Neumann : https://gcc.gnu.org/g:11f37868bb5812c4f0ac023909f5421595f68a43 commit r13-8555-g11f37868bb5812c4f0ac023909f5421595f68a43 Author: Thomas

[Bug ipa/113907] [11/12/13/14 regression] ICU miscompiled on x86 since r14-5109-ga291237b628f41

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113907 --- Comment #70 from Jan Hubicka --- Hello, over easter I did some analysis of the cases where ICF is now disabled due to jump function miscompare. Most common case (seen also on GCC) is the situation where function is originally static inline

[Bug tree-optimization/114557] New: ehcleanup cleanup_empty_eh_merge_phis eats a lot of memory

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114557 Bug ID: 114557 Summary: ehcleanup cleanup_empty_eh_merge_phis eats a lot of memory Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal

[Bug c++/114560] New: Compilation error when using _mm512_maskz_expandloadu_epi16 with only -mavx512vbmi2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114560 Bug ID: 114560 Summary: Compilation error when using _mm512_maskz_expandloadu_epi16 with only -mavx512vbmi2 Product: gcc Version: 11.4.0 Status: UNCONFIRMED

[Bug c/114558] GCC 13.2.1 encountered a segmentation fault error when compiling PyTorch.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114558 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment

[gcc r14-9745] Darwin: Do not emit .macinfo when dsymutil cannot consume it.

https://gcc.gnu.org/g:3c499f8f6f7d19b21d7047efabbe6396ee1c2cac commit r14-9745-g3c499f8f6f7d19b21d7047efabbe6396ee1c2cac Author: Iain Sandoe Date: Sun Mar 31 23:25:31 2024 +0100 Darwin: Do not emit .macinfo when dsymutil cannot consume it. Some verions of dsymutil do not ignore

[pushed] testsuite, Darwin: Allow for an undefined symbol [PR114036].

Tested on x86_64-darwin17,21,23 and on x86_64 and powerpc64 linux gnu, pushed to trunk, thanks Iain --- 8< --- Darwin's linker defaults to requiring all symbols to be defined at static link time (unless specifically noted or dynamic lookuo is enabled). For this test, we just need to note that

[Bug c++/114561] Comma operator with forwarding reference to pointer raises invalid lvalue required error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114561 --- Comment #2 from Jonathan Wakely --- Reduced: void* const NONE = nullptr; //Compiles void beforeParam(); template void create(U && u) noexcept { const void* const& r = ( (void) beforeParam(), u ); } void test_func() {

[Bug libstdc++/114553] Undefined symbol in directory_iterator move assignment operator with -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114553 --- Comment #2 from Jonathan Wakely --- (In reply to Toni Lammi from comment #0) > The issue does not seem to be present in trunk. It seems to be a change in inlining decisions on trunk, because the swap symbol still isn't exported from the

  1   2   3   4   5   >