Re: [PATCH] vect: Use factored nloads for load cost modeling [PR82255]

Hi Richard, on 2021/1/15 下午8:03, Richard Biener wrote: > On Fri, Jan 15, 2021 at 9:11 AM Kewen.Lin wrote: >> >> Hi, >> >> This patch follows Richard's suggestion in the thread discussion[1], >> it's to factor out the nloads computation in vectorizable_load for >> strided access, to ensure we can

Re: [PATCH] rs6000: Use rldimi for vec init instead of shift + ior

on 2021/1/15 下午2:40, Kewen.Lin via Gcc-patches wrote: > Hi Segher, > > on 2021/1/15 上午8:50, Segher Boessenkool wrote: >> Hi! >> >> On Tue, Dec 22, 2020 at 04:08:26PM +0800, Kewen.Lin wrote: >>> This patch is to make unsigned int vector init go with >>> rldimi to merge two integers instead of

Re: [PATCH] combine: zeroing cost for new copies

Hi Segher, on 2021/1/15 下午2:49, Kewen.Lin via Gcc-patches wrote: > on 2021/1/15 上午4:43, Segher Boessenkool wrote: [snip...] >> Long ago I had the following patch for this. Not sure why I never >> submitted it, maybe there is something wronmg with it? >> > > If you don't mind, I'll do a check

Re: [committed] Skip asm goto test fails on hppa

On Mon, 18 Jan 2021, John David Anglin wrote: > The hppa target is a reload target and asm goto is not supported on reload > targets. > Skip failing tests on hppa. IIUC the preferred term is "IRA target" or maybe "non-LRA target", as opposed to "LRA target". The tests fail for cris-elf too,

Re: [PATCH,rs6000] Optimize pcrel access of globals [ping]

Ping. Aaron Sawdey, Ph.D. saw...@linux.ibm.com IBM Linux on POWER Toolchain > On Dec 9, 2020, at 11:04 AM, acsaw...@linux.ibm.com wrote: > > From: Aaron Sawdey > > Ping. I've folded in the changes to comments suggested by Will Schmidt. > > This patch implements a RTL pass that looks for

Re: [PATCH,rs6000] Test cases for p10 fusion patterns

Ping. Aaron Sawdey, Ph.D. saw...@linux.ibm.com IBM Linux on POWER Toolchain > On Jan 3, 2021, at 2:44 PM, Aaron Sawdey wrote: > > Ping. > > Aaron Sawdey, Ph.D. saw...@linux.ibm.com > IBM Linux on POWER Toolchain > > >> On Dec 11, 2020, at 1:53 PM, acsaw...@linux.ibm.com wrote: >> >>

Re: [PATCH,rs6000] Fusion patterns for logical-logical

Ping. Aaron Sawdey, Ph.D. saw...@linux.ibm.com IBM Linux on POWER Toolchain > On Jan 3, 2021, at 2:43 PM, Aaron Sawdey wrote: > > Ping. > > Aaron Sawdey, Ph.D. saw...@linux.ibm.com > IBM Linux on POWER Toolchain > > >> On Dec 10, 2020, at 8:41 PM, acsaw...@linux.ibm.com wrote: >> >>

Re: [PATCH,rs6000] Combine patterns for p10 load-cmpi fusion

Ping. Aaron Sawdey, Ph.D. saw...@linux.ibm.com IBM Linux on POWER Toolchain > On Jan 3, 2021, at 2:42 PM, Aaron Sawdey wrote: > > Ping. > > I assume we’re going to want a separate patch for the new instruction type. > > Aaron Sawdey, Ph.D. saw...@linux.ibm.com > IBM Linux on POWER

Re: [PATCH] RISC-V: The 'multilib-generator' enhancement.

Hi Geng Qi: Thanks for your patch, committed! On Mon, Jan 18, 2021 at 3:01 PM Geng Qi via Gcc-patches wrote: > > From: gengqi > > Think about this case: > ./multilib-generator rv32imc-ilp32-rv32imac,rv32imacxthead-f > Here are 2 problems: > 1. A unexpected 'xtheadf' extension was made. >

Re: [PATCH] [PR rtl/optimization/98694] Fix incorrect optimization by cprop_hardreg.

On Mon, Jan 18, 2021 at 7:10 PM Richard Sandiford wrote: > > Hongtao Liu writes: > > On Mon, Jan 18, 2021 at 6:18 PM Richard Sandiford > > wrote: > >> > >> Hongtao Liu via Gcc-patches writes: > >> > Hi: > >> > If SRC had been assigned a mode narrower than the copy, we can't link > >> > DEST

Go patch committed: Read embedcfg file, parse go:embed directives

This patch to the Go frontend reads go:embed directives and attaches them to variables. It also reads the embedcfg file passed on the command line. We still don't actually do anything with the directives. Bootstrapped and ran Go testsuite on x86_64-pc-linux-gnu. Committed to mainline. Ian

[committed] Minor fix to pr41445-7 testcase

The addition of the dg-skip-if for AIX changes the line number for the variable declarations in the file which are checked by the dg-final directives.  Thus those directives need a trivial update. Committed to the trunk Jeff commit 9a3ab93ceb23fbe45bfbc597d88f208fe092ea14 Author: Jeff Law

libbacktrace patch committed: Don't fail tests if dwz fails

On my system the current version of dwz fails on some DWARF 5 input. This is reportedly fixed by https://sourceware.org/pipermail/dwz/2021q1/000775.html, but in the meantime there is no reason for the libbacktrace testsuite to fail just because dwz fails. This patch changes the Makefile so that

libbacktrace patch committed: Use correct DWARF-5 filename index

This libbacktrace patch uses the correct directory and filename index for DWARF 5. For DWARF 4 and before, the zero entry for the directory and filename information stored in the line program came from the compilation unit. Because of that, the old code used to handle zero specially, and

Re: [PATCH] c++: ICE with USING_DECL redeclaration [PR98687]

On 1/15/21 12:26 AM, Marek Polacek wrote: My recent patch that introduced push_using_decl_bindings didn't handle USING_DECL redeclaration, therefore things broke. This patch amends that. Note that I don't know if the other parts of finish_nonmember_using_decl are needed (e.g. the binding->type

[PATCH] fwprop: Allow (subreg (mem)) simplifications

Boostrapped and regtested on x86_64-redhat-linux, ppc64le-redhat-linux and s390x-redhat-linux. I realize it might be too late for a change like this, but it's desirable to have this in conjunction with the https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563799.html s390 regression fix,

[PATCH] IBM Z: Fix usage of "f" constraint with long doubles

Bootstrapped and regtested on s390x-redhat-linux. Depends on https://gcc.gnu.org/pipermail/gcc-patches/2021-January/562898.html; ok for master once the dependency is committed? After switching the s390 backend to store long doubles in vector registers, "f" constraint broke when used with the

Re: [C PATCH] qualifiers of pointers to arrays in C2X [PR 98397]

On Sun, 17 Jan 2021, Uecker, Martin wrote: > I did not add tests for c11 for warnings because we already > had warnings before and the tests for these exist. (I removed  > -Wdiscarded-array-qualifiers from the old tests as this flag > is not needed.) Or should there be additional warnings > with

[committed] IRA: patch to fix PR97847

The following patch fixes   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97847 The patch was successfully bootstrapped and tested on x86-64 and ppc64. [PR97847] IRA: Skip abnormal critical edge splitting PPC64 can generate jumps with clobbered pseudo-regs and a BB with such jump can have

[committed] c++: Add CTAD + pack expansion testcase

After r11-6614 made cp_walk_subtrees walk into the template of a CTAD placeholder, we now correctly accept the below testcase. We used to reject it because find_parameter_packs_r would fail to find the parameter pack Ts inside the CTAD placeholder within the pack expansion.

[r11-6759 Regression] FAIL: gcc.dg/debug/dwarf2/pr41445-7.c scan-assembler DW_TAG_variable[^\\r\\n]*[\\r\\n]+[^\\r\\n]*"varj[^\\r\\n]*DW_AT_name([^\\r\\n]*[\\r\\n]+[^\\r\\n]*DW_AT_)*[^\\r\\n]*[\\r\\n]

On Linux/x86_64, b654d23a470af25442e496ba62b5558e7c3ff1e6 is the first bad commit commit b654d23a470af25442e496ba62b5558e7c3ff1e6 Author: David Edelsohn Date: Sun Jan 17 18:18:56 2021 -0500 testsuite: Skip DWARF 5 testcases on AIX. caused FAIL: gcc.dg/debug/dwarf2/pr41445-7.c

Re: [PATCH] Hurd: Enable ifunc by default

Hello, Joseph Myers, le lun. 18 janv. 2021 20:05:44 +, a ecrit: > On Wed, 13 Jan 2021, Thomas Schwinge wrote: > > Thanks (and sorry for the delay), pushed "Hurd: Enable ifunc by default" > > to master branch in commit e9cb89b936f831a02318d45fc4ddb06f7be55ae4, and > > cherry-picked into

Re: [PATCH] libbacktrace: Fix up DWARF5 .debug_line handling [PR98716]

On Mon, Jan 18, 2021 at 12:11:02PM -0800, Ian Lance Taylor wrote: > Thanks, but I think more changes are needed. Looking up entries in > the filenames array will be off by one for DWARF 5 in other places as > well, specifically when handling DW_LNS_set_file and DW_AT_call_file. > I'm testing a

Re: [PATCH] libbacktrace: Fix up DWARF5 .debug_line handling [PR98716]

On Mon, Jan 18, 2021 at 10:44 AM Jakub Jelinek via Gcc-patches wrote: > > When GCC (since the switch to -gdwarf-5 by default) is configured and built > against recent binutils (2.35.1 if slightly patched, or 2.36 or trunk), > the assembler emits DWARF5 .debug_line rather than DWARF4 or older >

Re: [PATCH] Hurd: Enable ifunc by default

On Wed, 13 Jan 2021, Thomas Schwinge wrote: > Hi! > > Thanks (and sorry for the delay), pushed "Hurd: Enable ifunc by default" > to master branch in commit e9cb89b936f831a02318d45fc4ddb06f7be55ae4, and > cherry-picked into releases/gcc-10 branch in commit >

[PATCH] ipa-sra: Do not remove return values needed because of non-call EH (PR 98690)

Hi, IPA-SRA already contains a check to figure out that an otherwise dead parameter is actually required because of non-call exceptions, but it is not present at the equivalent spot where SRA figures out whether the return statement is used for anything useful. This patch adds that condition

Re: [PATCH] Modula-2 into the GCC tree on master

Matthias Klose writes: > this is mising the definition of lang_register_spec_functions for the jit > build. > > 2020-03-23 Matthias Klose > > * jit-spec.c (lang_register_spec_functions): New, not used for jit. > > > --- a/gcc/jit/jit-spec.c > +++ b/gcc/jit/jit-spec.c > @@ -39,3 +39,9

Re: [PATCH] aarch64: reimplement vqmovn_high* intrinsics using builtins

Kyrylo Tkachov via Gcc-patches writes: > diff --git a/gcc/config/aarch64/aarch64-simd-builtins.def > b/gcc/config/aarch64/aarch64-simd-builtins.def > index > 6efc7706a41e02d947753a4cda984159b68bd39f..27e9026d9e8b7ff980c5b8d9ff1b00490e3a18cb > 100644 > ---

[PATCH] libbacktrace: Fix up DWARF5 .debug_line handling [PR98716]

Hi! When GCC (since the switch to -gdwarf-5 by default) is configured and built against recent binutils (2.35.1 if slightly patched, or 2.36 or trunk), the assembler emits DWARF5 .debug_line rather than DWARF4 or older .debug_line. Seems some DWARF5 support has been added to libbacktrace, but

[committed] widening_mul: Fix up signed multiplication overflow check handling [PR98727]

Hi! I forgot one line, which means that if the second operand of the multiplication isn't constant, it would be just the same as the first one. Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, committed as obvious to trunk. 2021-01-18 Jakub Jelinek PR

Re: [PATCH] aix: Default to DWARF 4

On Mon, Jan 18, 2021 at 11:49 AM Jakub Jelinek wrote: > > On Mon, Jan 18, 2021 at 11:31:37AM -0500, David Edelsohn via Gcc-patches > wrote: > > On Mon, Jan 18, 2021 at 6:01 AM Mark Wielaard wrote: > > > > > > Hi David, > > > > > > On Sun, Jan 17, 2021 at 06:12:06PM -0500, David Edelsohn wrote:

[Patch] OpenMP/Fortran: Fixes for {use,is}_device_ptr [PR98476]

use_device_ptr and is_device_ptr are underspecified for Fortran in OpenMP <= 5.0 and, hence, also not properly implemented in GCC. OpenMP 5.1 cleaned this up by mapping (for Fortran) use_device_ptr to the existing and well-defined use_device_addr (except for type(c_ptr)) and is_device_ptr (with

Re: [PATCH] aix: Default to DWARF 4

Hi David, On Mon, 2021-01-18 at 11:31 -0500, David Edelsohn wrote: > On Mon, Jan 18, 2021 at 6:01 AM Mark Wielaard wrote: > > Thanks, I hadn't tested against AIX. Could you also update > > gcc/doc/invoke.texi (-gdwarf) with the defaults for AIX? > > Other targets override the default DWARF

Re: [PATCH] aix: Default to DWARF 4

On Mon, Jan 18, 2021 at 11:31:37AM -0500, David Edelsohn via Gcc-patches wrote: > On Mon, Jan 18, 2021 at 6:01 AM Mark Wielaard wrote: > > > > Hi David, > > > > On Sun, Jan 17, 2021 at 06:12:06PM -0500, David Edelsohn wrote: > > > GCC now defaults to DWARF 5. AIX only supports DWARF 4 (3.5).

Re: [PATCH] aix: Default to DWARF 4

On Mon, Jan 18, 2021 at 6:01 AM Mark Wielaard wrote: > > Hi David, > > On Sun, Jan 17, 2021 at 06:12:06PM -0500, David Edelsohn wrote: > > GCC now defaults to DWARF 5. AIX only supports DWARF 4 (3.5). > > > > This patch overrides the default DWARF version to 4 unless explicitly > >

Re: The performance data for two different implementation of new security feature -ftrivial-auto-var-init

> On Jan 18, 2021, at 7:09 AM, Richard Sandiford > wrote: > > Qing Zhao writes: > D will keep all initialized aggregates as aggregates and live which > means stack will be allocated for it. With A the usual optimizations > to reduce stack usage can be applied. I

[PATCH 2/n] AVR CC0 conversion - adjust peepholes

Hi, This patch, to be applied on top of https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563638.html, adjusts peepholes to match and generate parallels with a clobber of REG_CC. It also sets mov_insn as the name of the pattern for the split insn (rather than the define_insn_and_split), so

[commited] Avoid no-stack-protector-attr fails on hppa*-*-*

The stack grows up on hppa and stack protection is not supported. Committed to master. Regards, Dave Avoid no-stack-protector-attr fails on hppa*-*-*. gcc/testsuite/ChangeLog: * g++.dg/no-stack-protector-attr-3.C: Don't compile on hppa*-*-*. * g++.dg/no-stack-protector-attr.C:

[committed] Skip asm goto test fails on hppa

The hppa target is a reload target and asm goto is not supported on reload targets. Skip failing tests on hppa. Committed to master. Regards, Dave Skip asm goto tests on hppa*-*-*. gcc/testsuite/ChangeLog: PR testsuite/97987 * gcc.c-torture/compile/asmgoto-2.c: Skip on hppa.

[PATCH] aarch64: Use GCC vector extensions for integer mls intrinsics

Hi, As subject, this patch rewrites integer mls Neon intrinsics to use a - b * c rather than inline assembly code, allowing for better scheduling and optimization. Regression tested and bootstrapped on aarch64-none-linux-gnu - no issues. If ok, please commit to master (I don't have commit

Re: [backport gcc10, gcc9] Requet to backport PR97969

On 2021-01-18 7:50 a.m., Richard Biener wrote: On Mon, 18 Jan 2021, Przemyslaw Wirkus wrote: Hi all, Can we backport PR97969 patch to GCC 10 and (maybe) GCC 9 ?: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97969 IMHO bug is severe and could land in GCC 10 and 9. Vladimir's original patch:

Re: [PATCH] PING implement pre-c++20 contracts

On 1/4/21 9:58 AM, Jeff Chapman wrote: Ping. re: https://gcc.gnu.org/pipermail/gcc-patches/2020-December/561135.html > OK, I'll start with -alt then, thanks. Andrew is exactly correct, contracts-jac-alt is still

Re: [PATCH] analyzer: use "malloc" attribute

On Mon, 2021-01-18 at 14:26 +0100, Richard Biener wrote: > On Sun, 17 Jan 2021, David Malcolm wrote: > > > This is an updated version of this patch from October: > > > > 'RFC: add "deallocated_by" attribute for use by analyzer' > > > >

[committed] libstdc++: Only test writing to wostream if supported [PR 98725]

libstdc++-v3/ChangeLog: PR libstdc++/98725 * testsuite/20_util/unique_ptr/io/lwg2948.cc: Do not try to write to a wide character stream if wide character support is disabled in the library. Tested powerpc64le-linux. Committed to trunk. commit

[PATCH] testsuite/97494 - adjust gcc.dg/vect/slp-11b.c

Support for loop SLP splitting exposed that slp-11b.c has folding that breaks SLP discovery which isn't what was intended when the testcase was written. The following makes it SLP-able and "only" run into the issue that a load permutation is required. And tries to adjust the target selectors

Re: [PATCH] alias: Fix offset checks involving section anchors [PR92294]

Jan Hubicka writes: >> >> >> >> Well, in tree-ssa code we do assume these to be either disjoint objects >> >> or equal (in decl_refs_may_alias_p that continues in case >> >> compare_base_decls is -1). I am not sure if we win much by threating >> >> them differently on RTL level. I would preffer

[arm,testsuite]: Fix options for vceqz_p64.c and vceqzq_p64.c

These two tests need: dg-require-effective-target arm_crypto_ok dg-add-options arm_crypto because they use intrinsics that need -mfpu=crypto-neon-fp-armv8. Committed as obvious. 2021-01-18 Christophe Lyon gcc/testsuite/ PR target/71233 *

Re: [PATCH] libgomp: enable linux-futex on riscv64

On Mon, Jan 18, 2021 at 03:04:11PM +0100, Andreas Schwab wrote: > Regtested on riscv64-suse-linux. > > libgomp/ > * configure.tgt (riscv64*-*-linux*): Add linux to config_path. Ok, thanks. > --- a/libgomp/configure.tgt > +++ b/libgomp/configure.tgt > @@ -64,6 +64,10 @@ if test

[PATCH] libgomp: enable linux-futex on riscv64

Regtested on riscv64-suse-linux. libgomp/ * configure.tgt (riscv64*-*-linux*): Add linux to config_path. --- libgomp/configure.tgt | 4 1 file changed, 4 insertions(+) diff --git a/libgomp/configure.tgt b/libgomp/configure.tgt index be06be0e52b..fe2bf1dac51 100644 ---

Re: [PATCH] Modula-2 into the GCC tree on master

Richard Biener writes: Hello Richard, many thanks for taking the time to review the patches and tarball. > It looks like libgm2 is built independently on whether m2 is enabled or not? > I'd like to see a while-listing of supported targets like done for example > for libgomp via configure.tgt

[PATCH] testsuite/97299 - fix test condition of gcc.dg/vect/slp-reduc-3.c

This avoids looking for permute optimization when SLP cannot be applied. Pushed. 2021-01-18 Richard Biener PR testsuite/97299 * gcc.dg/vect/slp-reduc-3.c: Guard VEC_PERM_EXPR scan. --- gcc/testsuite/gcc.dg/vect/slp-reduc-3.c | 3 ++- 1 file changed, 2 insertions(+), 1

Re: [PATCH] alias: Fix offset checks involving section anchors [PR92294]

> >> > >> Well, in tree-ssa code we do assume these to be either disjoint objects > >> or equal (in decl_refs_may_alias_p that continues in case > >> compare_base_decls is -1). I am not sure if we win much by threating > >> them differently on RTL level. I would preffer staying consistent here.

Re: [PATCH] analyzer: use "malloc" attribute

On Sun, 17 Jan 2021, David Malcolm wrote: > This is an updated version of this patch from October: > > 'RFC: add "deallocated_by" attribute for use by analyzer' > https://gcc.gnu.org/pipermail/gcc-patches/2020-October/44.html > > reworking it to build on top of Martin's work as noted

Re: [PATCH] keep scope blocks for all inlined functions (PR 98664)

On Sun, Jan 17, 2021 at 1:46 AM Martin Sebor wrote: > > On 1/15/21 12:44 AM, Richard Biener wrote: > > On Thu, Jan 14, 2021 at 8:13 PM Martin Sebor via Gcc-patches > > wrote: > >> > >> One aspect of PR 98465 - Bogus warning stringop-overread for std::string > >> is the inconsistency between -g

GCC 11.0.0 Status Report (2021-01-18), Stage 4 in effect now

Status == GCC trunk which eventually will become GCC 11 is now in regression and documentation fixes only mode (Stage 4). Please help triaging and fixing regressions to make a timely release of GCC 11 possible. Quality Data Priority # Change from last report

Re: The performance data for two different implementation of new security feature -ftrivial-auto-var-init

Qing Zhao writes: D will keep all initialized aggregates as aggregates and live which means stack will be allocated for it. With A the usual optimizations to reduce stack usage can be applied. >>> >>> I checked the routine “poverties::bump_map” in 511.povray_r since it >>> has a

[committed] libstdc++: Fix narrow char test to use stringbuf not wstringbuf

This seems to be a copy & paste error. libstdc++-v3/ChangeLog: * testsuite/27_io/basic_stringstream/cons/char/1.cc: Use stringbuf not wstringbuf. Tested x86_64-linux. Committed to trunk. commit a81d2f1e414836549b909f2de927b6ae10e8b156 Author: Jonathan Wakely Date: Mon Jan 18

Re: [backport gcc10, gcc9] Requet to backport PR97969

On Mon, 18 Jan 2021, Przemyslaw Wirkus wrote: > Hi all, > > Can we backport PR97969 patch to GCC 10 and (maybe) GCC 9 ?: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97969 > > IMHO bug is severe and could land in GCC 10 and 9. Vladimir's original patch: >

Re: [PATCH] Modula-2 into the GCC tree on master

On 1/18/21 2:09 AM, Gaius Mulley via Gcc-patches wrote: > gcc/ > > * gcc/brig/brigspec.c (lang_register_spec_functions): Added. > * gcc/c-family/cppspec.c (lang_register_spec_functions): Added. > * gcc/c/gccspec.c (lang_register_spec_functions): Added. > * gcc/cp/g++spec.c

Re: [PATCH] alias: Fix offset checks involving section anchors [PR92294]

Richard Biener writes: > On Mon, 18 Jan 2021, Jan Hubicka wrote: > >> > This is a repost of: >> > >> > https://gcc.gnu.org/pipermail/gcc-patches/2020-February/539763.html >> > >> > which was initially posted during stage 4. (And yeah, I only just >> > missed stage 4 again.) >> > >> > IMO it

Re: [PATCH] [WIP] openmp: Add OpenMP 5.0 task detach clause support

Hi Jakub, > On Sun, Jan 17, 2021 at 04:25:24PM +0100, Andreas Schwab wrote: >> On Jan 17 2021, Jakub Jelinek via Gcc-patches wrote: >> >> > Kwok, I guess you can reproduce it even on Linux with --disable-linux-futex >> >> And all targets that are not explicitly configured in >>

Re: BoF DWARF5 patches (25% .debug section size reduction)

> On 15/01/2021 17:16, Jakub Jelinek via Gcc-patches wrote: > > On Sun, Nov 15, 2020 at 11:41:24PM +0100, Mark Wielaard wrote: > >> From: Mark Wielaard > >> Date: Tue, 29 Sep 2020 15:52:44 +0200 > >> Subject: [PATCH] Default to DWARF5 > >> > >> gcc/ChangeLog: > >> > >>* common.opt (gdwarf-):

Re: [PATCH] [PR rtl/optimization/98694] Fix incorrect optimization by cprop_hardreg.

Hongtao Liu writes: > On Mon, Jan 18, 2021 at 6:18 PM Richard Sandiford > wrote: >> >> Hongtao Liu via Gcc-patches writes: >> > Hi: >> > If SRC had been assigned a mode narrower than the copy, we can't link >> > DEST into the chain even they have same >> > hard_regno_nregs(i.e. HImode/SImode

Re: [r11-6755 Regression] FAIL: libstdc++-prettyprinters/libfundts.cc print os on Linux/x86_64

Hi, On Sun, Jan 17, 2021 at 11:30:59AM -0800, sunil.k.pandey wrote: > On Linux/x86_64, > > 3804e937b0e252a7e42632fe6d9f898f1851a49c is the first bad commit > commit 3804e937b0e252a7e42632fe6d9f898f1851a49c > Author: Mark Wielaard > Date: Tue Sep 29 15:52:44 2020 +0200 > > Default to

Re: [PATCH] aix: Default to DWARF 4

Hi David, On Sun, Jan 17, 2021 at 06:12:06PM -0500, David Edelsohn wrote: > GCC now defaults to DWARF 5. AIX only supports DWARF 4 (3.5). > > This patch overrides the default DWARF version to 4 unless explicitly > stated. > > gcc/ChangeLog: > > *

Re: [PATCH] [PR rtl/optimization/98694] Fix incorrect optimization by cprop_hardreg.

On Mon, Jan 18, 2021 at 6:43 PM Hongtao Liu wrote: > > On Mon, Jan 18, 2021 at 6:18 PM Richard Sandiford > wrote: > > > > Hongtao Liu via Gcc-patches writes: > > > Hi: > > > If SRC had been assigned a mode narrower than the copy, we can't link > > > DEST into the chain even they have same > >

[backport gcc10, gcc9] Requet to backport PR97969

Hi all, Can we backport PR97969 patch to GCC 10 and (maybe) GCC 9 ?: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97969 IMHO bug is severe and could land in GCC 10 and 9. Vladimir's original patch: https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563322.html applies without changes to both

Re: [PATCH] [PR rtl/optimization/98694] Fix incorrect optimization by cprop_hardreg.

On Mon, Jan 18, 2021 at 6:18 PM Richard Sandiford wrote: > > Hongtao Liu via Gcc-patches writes: > > Hi: > > If SRC had been assigned a mode narrower than the copy, we can't link > > DEST into the chain even they have same > > hard_regno_nregs(i.e. HImode/SImode in i386 backend). > > In

Re: [PATCH] Modula-2 into the GCC tree on master

On Mon, Jan 18, 2021 at 2:09 AM Gaius Mulley via Gcc-patches wrote: > > > Hello, > > here is a patch which merges the gm2 front end into the GCC tree. The > patches have been boostrapped under x86_64 GNU/Linux Debian Stretch > built using make -j 24 and also under x86_64 GNU/Linux Debian Buster

Re: BoF DWARF5 patches (25% .debug section size reduction)

On 15/01/2021 17:16, Jakub Jelinek via Gcc-patches wrote: On Sun, Nov 15, 2020 at 11:41:24PM +0100, Mark Wielaard wrote: On Tue, 2020-09-29 at 15:56 +0200, Mark Wielaard wrote: On Thu, 2020-09-10 at 13:16 +0200, Jakub Jelinek wrote: On Wed, Sep 09, 2020 at 09:57:54PM +0200, Mark Wielaard

Re: [PATCH] [PR rtl/optimization/98694] Fix incorrect optimization by cprop_hardreg.

Hongtao Liu via Gcc-patches writes: > Hi: > If SRC had been assigned a mode narrower than the copy, we can't link > DEST into the chain even they have same > hard_regno_nregs(i.e. HImode/SImode in i386 backend). In general, changes between modes within the same hard register are OK. Could you

[PATCH] libstdc++: Add workaround for as Error: file number less than one error [PR98708]

Hi! As mentioned in the PR, since the switch to DWARF5 by default instead of DWARF4, gcc fails to build when configured against recent binutils. The problem is that cxx11-ios_failure* is built in separate steps, -S compilation (with -g -O2) followed by some sed and followed by -c -g -O2 -g0

[PATCH] [PR rtl/optimization/98694] Fix incorrect optimization by cprop_hardreg.

Hi: If SRC had been assigned a mode narrower than the copy, we can't link DEST into the chain even they have same hard_regno_nregs(i.e. HImode/SImode in i386 backend). i.e kmovw %k0, %edi vmovd %edi, %xmm2 vpshuflw$0, %xmm2, %xmm0 kmovw %k0, %r8d

Re: [stage1][PATCH] Change semantics of -frecord-gcc-switches and add -frecord-gcc-switches-format.

On 1/15/21 8:14 PM, Alexandre Oliva wrote: Hello, Martin, Our testing detected unexpected -dumpbase-ext options making to the producer string. I tracked it down to something weird that happened in this patch: On Dec 4, 2020, Martin Liška wrote: +++ b/gcc/dwarf2out.c - case

Re: [PATCH] alias: Fix offset checks involving section anchors [PR92294]

On Mon, 18 Jan 2021, Jan Hubicka wrote: > > This is a repost of: > > > > https://gcc.gnu.org/pipermail/gcc-patches/2020-February/539763.html > > > > which was initially posted during stage 4. (And yeah, I only just > > missed stage 4 again.) > > > > IMO it would be better to fix the bug