Re: [PATCH] ipa: silent -Wodr notes with -w

PING^1 On 12/2/22 12:27, Martin Liška wrote: > If -w is used, warn_odr properly sets *warned = false and > so it should be preserved when calling warn_types_mismatch. > > Noticed that during a LTO reduction where I used -w. > > Patch can bootstrap on x86_64-linux-gnu and survives regression test

Re: [PATCH] IPA: do not release body if still needed

PING^1 On 12/1/22 10:59, Martin Liška wrote: > Hi. > > Noticed during building of libbackend.a with the LTO partial linking. > > The function release_body is called even if clone_of is a clone > of a another function and thus it shares tree declaration. We should > preserve it in that situation.

Re: [PATCH] i386: fix assert (__builtin_cpu_supports ("x86-64") >= 0)

On 12/7/22 12:27, Jakub Jelinek wrote: > On Fri, Nov 25, 2022 at 01:57:35PM +0100, Martin Liška wrote: >> PR target/107551 >> >> gcc/ChangeLog: >> >> * config/i386/i386-builtins.cc (fold_builtin_cpu): Use same path >> as for PR103661. >> * doc/extend.texi: Fix "x86-64" use. >> >> gcc

Re: [PATCH] i386: fix assert (__builtin_cpu_supports ("x86-64") >= 0)

On Fri, Dec 09, 2022 at 10:18:34AM +0100, Martin Liška wrote: > I'm going to push the revision. > > What exactly do you mean by random? I just know there are differences in > between > x86 and ppc: > > int __builtin_cpu_supports(const char *feature) > This function returns a positive integer if

[PATCH v3] LoongArch: Fixed a compilation failure with '%c' in inline assembly [PR107731].

There is description of '%c' "%n" "%a" and "%l" in section 17.5 of gccint.pdf. So I can understand that these descriptors are the ones that the common code implementation back end has to support, right? But I don't see the use of these descriptors in gcc.pdf.Now I want to add the descriptor informa

Re: [PATCH v3] LoongArch: Fixed a compilation failure with '%c' in inline assembly [PR107731].

Lulu Cheng writes: > There is description of '%c' "%n" "%a" and "%l" in section 17.5 of gccint.pdf. > So I can understand that these descriptors are the ones that the common code > implementation back end has to support, right? > But I don't see the use of these descriptors in gcc.pdf.Now I want t

[PATCH] Backport gcc-12: jobserver FIFO support

Hi. As make 4.4 has been release, it switches to FIFO by default. That makes troubles to the latest GCC release, version 12. Right now, we've been using the following 4 patches in openSUSE gcc12 package: 1270ccda70ca09f7d4fe76b5156dca8992bd77a6 53e3b2bf16a486c15c20991c6095f7be09012b55 fed766af32e

Re: [PATCH Rust front-end v4 46/46] gccrs: Add README, CONTRIBUTING and compiler logo

On 12/6/22 11:14, arthur.co...@embecosm.com wrote: > |We still need to write out a documentation section, but these READMEs will > help in the meantime.| Hello. Just a quick comment: The Sphinx conversion didn't make it for all GCC manuals. However, you can still use Sphinx for a newly created

Re: [PATCH 3/3]rs6000: NFC no need copy_rtx in rs6000_emit_set_long_const and rs6000_emit_set_const

Jiufu Guo via Gcc-patches writes: > Hi Kewen, > > 在 12/1/22 11:31 AM, Kewen.Lin 写道: >> Hi Jeff, >> >> on 2022/12/1 09:36, Jiufu Guo wrote: >>> Hi, >>> >>> Function rs6000_emit_set_const/rs6000_emit_set_long_const are only invoked >>> from >>> two "define_split"s where the target operand is limi

Re: Rust front-end patches v4

On 12/6/22 11:13, arthur.co...@embecosm.com wrote: > Similarly to the previous round of patches, this patchset does not contain any > new features - only fixes for the reviews of the v3. New features will follow > shortly once that first patchset is merged. > > Once again, thank you to all the con

[PATCH] Fix memory constraint on MVE v[ld/st][2/4] instructions [PR107714]

Hi all, In the M-Class Arm-ARM: https://developer.arm.com/documentation/ddi0553/bu/?lang=en these MVE instructions only have '!' writeback variant and at: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107714 we found that the Um constraint would also allow through a register offset writeback,

[PATCH] gcov: Fix -fprofile-update=atomic

The code coverage support uses counters to determine which edges in the control flow graph were executed. If a counter overflows, then the code coverage information is invalid. Therefore the counter type should be a 64-bit integer. In multithreaded applications, it is important that the counter i

[PATCH 10/15 V5] arm: Implement cortex-M return signing address codegen

Hi Richard, thanks for reviewing. Richard Earnshaw writes: > On 07/11/2022 08:57, Andrea Corallo via Gcc-patches wrote: >> Hi all, >> please find attached the lastest version of this patch incorporating >> some >> more improvents. Feel free to ignore V3. >> Best Regards >>Andrea >> > >> A

[PATCH] AArch64: Enable TARGET_CONST_ANCHOR

Enable TARGET_CONST_ANCHOR to allow complex constants to be created via immediate add. Use a 24-bit range as that enables a 3 or 4-instruction immediate to be replaced by 2 additions. Fix the costing of immediate add to support 24-bit immediate and 12-bit shifted immediates. The generated code

Re: [Patch] libgomp: Handle OpenMP's reverse offloads

On Tue, Dec 06, 2022 at 08:45:07AM +0100, Tobias Burnus wrote: > 32bit vs. 64bit: libgomp itself is compiled with both -m32 and -m64; however, > nvptx and gcn requires -m64 on the device side and assume that the device > pointers are representable on the host (i.e. all are 64bit). The new code > tr

Re: [PATCH] AArch64: Enable TARGET_CONST_ANCHOR

Wilco Dijkstra writes: > Enable TARGET_CONST_ANCHOR to allow complex constants to be created via > immediate add. > Use a 24-bit range as that enables a 3 or 4-instruction immediate to be > replaced by > 2 additions. Fix the costing of immediate add to support 24-bit immediate > and 12-bit shi

Patch ping

Hi! I'd like to ping a few pending patches: https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606973.html - PR107465 - c-family: Fix up -Wsign-compare BIT_NOT_EXPR handling https://gcc.gnu.org/pipermail/gcc-patches/2022-November/607104.html - PR107465 - c-family: Incremental fix for -W

[PATCH] initialize fde objects lazily

When registering an unwind frame with __register_frame_info_bases we currently initialize that fde object eagerly. This has the advantage that it is immutable afterwards and we can safely access it from multiple threads, but it has the disadvantage that we pay the initialization cost even if the a

[PATCH] i386: correct division modeling in lujiazui.md

Model the divider in Lujiazui processors as a separate automaton to significantly reduce the overall model size. This should also result in improved accuracy, as pipe 0 should be able to accept new instructions while the divider is occupied. It is unclear why integer divisions are modeled as if pi

[PATCH v2] RISC-V: Produce better code with complex constants [PR95632] [PR106602]

Changes since v1: - Fixed formatting issues. - Added a name to the define_insn_and_split pattern. - Set the target on the 'dg-do compile' in pr106602.c. - Removed the rv32 restriction in pr95632.c. -- >8 -- Due to RISC-V limitations on operations with big constants

[Patch] Fortran/OpenMP: align/allocator modifiers to the allocate clause

Implementing the 5.1 syntax inside the 'allocate' clause. That's a fallout of working on something else... OK for mainline? Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Tho

Re: [Patch] Fortran/OpenMP: align/allocator modifiers to the allocate clause

On Fri, Dec 09, 2022 at 09:14:55PM +0100, Tobias Burnus wrote: > Implementing the 5.1 syntax inside the 'allocate' clause. That's a > fallout of working on something else... > > OK for mainline? > > Tobias > - > Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 20

[Patch] Fortran: Replace simple '.' quotes by %<.%>

Found when working on the just submitted/committed patch. I intent to commit it to mainline as obvious tomorrow (or Sun or Mon), unless there are comments. Tobias - Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkt

[PATCH] Fortran: ICE on recursive derived types with allocatable components [PR107872]

Dear all, I am submitting the attached simple - and obvious - patch on behalf of Paul. It prevents a resource exhaustion due to an infinite loop, and has been regtested by multiple contributers, ;-) at least on x86_64-pc-linux-gnu. I intend to commit it to mainline within 24 hours, unless there

[PATCH] c++: extract_local_specs and unevaluated contexts [PR100295]

Here during partial instantiation of the constexpr if, extra_local_specs walks the statement looking for local specializations within to save and possibly capture. However, we're thwarted by the fact that 'ts' first appears inside an unevaluated context, and so the calls to process_outer_var_ref f

Re: [PATCH] Fortran: ICE on recursive derived types with allocatable components [PR107872]

Hi Harald, Thanks for doing that. My attention is elsewhere gfortran-wise. Good for mainline. Paul On Fri, 9 Dec 2022 at 21:27, Harald Anlauf via Fortran wrote: > Dear all, > > I am submitting the attached simple - and obvious - patch on > behalf of Paul. It prevents a resource exhaustion d

[PATCH v4 1/19] modula2 front end: changes outside gcc/m2, libgm2 and gcc/testsuite.

While writing the ChangeLog entries git gcc-verify spotted an oversight with v3 of this patch set. I had forgotten to post gm2.texi and also a tiny patchlet in gcc/configure.ac (to detect Python). HAVE_PYTHON is used within gcc/m2/Make-lang.in to avoid generating the library section included by

Re: Add zstd support to libbacktrace

On Wed, Dec 7, 2022 at 4:22 PM Ian Lance Taylor wrote: > > This patch adds zstd support to libbacktrace, to support the new > linker option --compress-debug-sections=zstd. This patch rewrites and simplifies the main zstd decompression loop using some ideas from the reference implementation. This

Prepare 'contrib/gcc-changelog/git_commit.py' for GCC/Rust (was: Rust front-end patches v4)

Hi! On 2022-12-06T12:03:56+0100, Richard Biener via Gcc-patches wrote: > On Tue, Dec 6, 2022 at 11:11 AM wrote: >> This patchset contains the fixed version of our most recent patchset. [...] > > Thanks a lot - this is OK to merge now Hey, hey! :-) Still working on some final edits to make t

Re: [PATCH] Backport gcc-12: jobserver FIFO support

On Fri, 2022-12-09 at 11:07 +0100, Martin Liška wrote: > Hi. > > As make 4.4 has been release, it switches to FIFO by default. That makes > troubles to the latest GCC release, version 12. Right now, we've been using > the following 4 patches in openSUSE gcc12 package: > > 1270ccda70ca09f7d4fe76b5

Add stub 'gcc/rust/ChangeLog' (was: Prepare 'contrib/gcc-changelog/git_commit.py' for GCC/Rust)

Hi! On 2022-12-10T07:39:24+0100, I wrote: > I've pushed "Prepare 'contrib/gcc-changelog/git_commit.py' for GCC/Rust" > to master branch in commit 325529e21e81fbc3561d2568cb7e8a26296e5b2f, see > attached. > > Please let me know if there is anything that I need to do to actually > generate the empty