Re: rust non-free-compatible trademark

On Mon, 2022-07-18 at 20:35 +0100, lkcl via Gcc wrote: > (apologies top-posting, strange mobile mailer). i would expect in that > case that the Rust Foundation to work closely with Certification Mark > Licensees, and to come to an accommodation, defining a subset if > necessary. > > if the gcc

Re: rust non-free-compatible trademark

On Mon, Jul 18, 2022 at 10:01 PM David Malcolm wrote: > Luke: you appear to me to be the one who is telling people what patches > they can and cannot apply, and it's pissing me off. 1) please don't you dare put words into my mouth that i did not state. first and only warning. 2) i'm sorry

Re: rust non-free-compatible trademark

(apologies top-posting, strange mobile mailer). i would expect in that case that the Rust Foundation to work closely with Certification Mark Licensees, and to come to an accommodation, defining a subset if necessary. if the gcc developers can clearly enunciate why shipping a "borrow checker"

Re: rust non-free-compatible trademark

a (private) discussion has, fascinatingly, uncovered this, from 1987: http://archive.adaic.com/pol-hist/policy/trademrk.txt In order to be a validated Ada compiler, a compiler must pass an extensive suite of programs called the Ada Compiler Validation Capability (ACVC). The AJPO has

[RFC] Function Multi Versioning on Arm

Hello, We are going to add Function Multiversioning [1] support to Arm architectures. The specification is made public as beta[2] to ensure toolchain that follows Arm C Language Extension will implement it in the same way. A few tweaks considered to make the developers' life easier. Since the

RE: [EXTERNAL] Re: Inquiry: Country of Origin for gfortran

Thank you for your help! -Original Message- From: Thomas Koenig Sent: Sunday, July 17, 2022 4:55 AM To: Zhang, Cynthia X. (GSFC-710.0)[TELOPHASE CORP] ; fort...@gcc.gnu.org; gcc mailing list Subject: [EXTERNAL] Re: Inquiry: Country of Origin for gfortran Hi Cynthia, > Hello, my

Re: rust non-free-compatible trademark

* lkcl via Gcc: > if the Rust Foundation were to add an extremely simple phrase > >"to be able to use the word rust in a distributed compiler your > modifications must 100% pass the test suite without modifying > the test suite" > > then all the problems and pain goes away. No. It

Marc Poulhies appointed Ada co-maintainer

I am pleased to announce that the GCC Steering Committee has appointed Marc Poulhies as Ada co-maintainer. Please join me in congratulating Marc on his new role. Marc, please update your listing in the MAINTAINERS file. Happy hacking! David

Re: rust non-free-compatible trademark

Hi Florian, On Mon, Jul 18, 2022, 20:33 Florian Weimer via Gcc wrote: > * lkcl via Gcc: > > > if the Rust Foundation were to add an extremely simple phrase > > > >"to be able to use the word rust in a distributed compiler your > > modifications must 100% pass the test suite without

Re: rust non-free-compatible trademark

> A Certification Mark is the proper way to formally and legally enforce such > requirements. BTW, nobody is or was at all confident that the Ada mark was legally enforcable. I'm in the camp that it isn't. > telling people they cannot patch the source code without permission Nobody is telling

Re: rust non-free-compatible trademark

> In order to be a validated Ada compiler, a compiler must pass > an extensive suite of programs called the Ada Compiler Validation > Capability (ACVC). FYI: the current name for this is ACATS: Ada Conformity Assessment Test Suite. >"to be able to use the word rust in a

Re: Marc Poulhies appointed Ada co-maintainer

Congratulations Marc! Very happy for you. You deserve all the best. Félicitations :) -- Arthur On Mon, Jul 18, 2022, 19:35 David Edelsohn via Gcc wrote: > I am pleased to announce that the GCC Steering Committee has appointed > Marc Poulhies as Ada co-maintainer. > > Please join me in

Re: rust non-free-compatible trademark

On 17/07/2022 18:31, Mark Wielaard wrote: Hi Luke, On Sun, Jul 17, 2022 at 04:28:10PM +0100, lkcl via Gcc wrote: with the recent announcement that rust is supported by gcc There is just a discussion about whether and how to integrate (portions) of the gccrs frontend into the main gcc

Re: rust non-free-compatible trademark

On Mon, Jul 18, 2022 at 8:09 AM David Brown wrote: > Speaking as someone who is neither a lawyer, nor a GCC developer, nor > even (as yet) a Rust user, it seems to me that step 1 would be to hear > what the Rust Foundation has to say on the matter: > >

Re: rust non-free-compatible trademark

On Mon, 18 Jul 2022 at 09:07, lkcl via Gcc wrote: > which is why i said - and have been ignored - that the gcc developers > need rather urgently to seek proper legal counsel and get a proper > legal opinion. You haven't been ignored. People have expressed reasonable disagreements with your

Re: rust non-free-compatible trademark

On Mon, Jul 18, 2022 at 9:50 AM Jonathan Wakely wrote: > You haven't been ignored. People have expressed reasonable > disagreements with your interpretation. > > Just because every line of your email hasn't been explicitly responded > to with positive acknowledgement of receipt doesn't mean

Re: [PATCH] aarch64: Replace manual swapping idiom with std::swap in aarch64.cc

Richard Ball writes: > Replace manual swapping idiom with std::swap in aarch64.cc > > gcc/config/aarch64/aarch64.cc has a few manual swapping idioms of the form: > > x = in0, in0 = in1, in1 = x; > > The preferred way is using the standard: > > std::swap (in0, in1); > > We should just fix these to

[committed] arc: Add ARCHS release 310a tune variant.

Add mtune and mcpu options for ARCHS release 310a type CPU. The mtune=release31a is designed to be used as an alternative to the mcpu=hs4x_rel31 option. ARCHS4x release 31a uses DSP instructions which are implemented a bit different than mpy9. Hence, use safer mpy2 option. gcc/ *

[Bug libstdc++/106320] [10 regression] build failure (due to view requirement changes?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106320 Patrick Palka changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug c++/106341] Template argument deduction of template value parameter crashes compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106341 --- Comment #2 from Liss Heidrich --- Created attachment 53315 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53315=edit output of gcc-11 when compiling segfault.cpp (from godbolt.org)

[Bug c++/106341] Template argument deduction of template value parameter crashes compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106341 --- Comment #1 from Liss Heidrich --- Created attachment 53314 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53314=edit output of gcc-10 when compiling segfault.cpp

[Bug d/103944] [12/13 Regression] Testsuite hang due to libphobos/testsuite/libphobos.gc/forkgc2.d

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103944 Matthias Klose changed: What|Removed |Added CC||doko at gcc dot gnu.org --- Comment

[Bug fortran/106331] [12/13 Regression] Whole array assignment of empty string segfaults with -Og since r12-2633-ge5e164effa30fd2b

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106331 --- Comment #5 from H.J. Lu --- The memory alignment passed to __builtin_memset shouldn't be 16 bytes in this case.

[Bug target/106322] i386: Wrong code at O2 level (O0 / O1 are working)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106322 --- Comment #9 from Mathieu Malaterre --- (In reply to Andrew Pinski from comment #8) > Does -fwrapv fix the issue? No. This seems like the exact same symptoms: % ./tests/mul_test

[Bug ipa/105676] [12/13 Regression] Bogus `-Wsuggest-attribute=pure` on function marked `__attribute__((const))` since r12-5437-g09a4ffb72aa2f513

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105676 --- Comment #3 from Jan Hubicka --- Such code is not that obviously safe. It is possible that getval will get inlined to some calls and not other within single function. In that case the calling function will read and modify cache variable

Re: [PATCH] Simplify branching in algos

On Mon, 18 Jul 2022 at 11:25, François Dumont wrote: > > Hi > > I just noticed that I still had this nice enhancement in my local > branches. > > Ok to commit ? OK, thanks.

[Bug middle-end/106314] GTY fails on virtual int but not virtual void

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106314 --- Comment #5 from Richard Biener --- (In reply to Aldy Hernandez from comment #4) > (In reply to Richard Biener from comment #3) > > GC only supports POD-like data structures, esp. proper inheritance is not > > supported so supporting virtual

[committed 1/2] arc: Fix interrupt's epilogue.

The stack pointer adjustment in interrupt epilogue is happening after restoring the ZOL registers which is wrong. Fixing this. gcc/ * config/arc/arc.cc (arc_expand_epilogue): Adjust the frame pointer first when in interrupts. gcc/testsuite/ *

[Bug fortran/106331] [12/13 Regression] Whole array assignment of empty string segfaults with -Og since r12-2633-ge5e164effa30fd2b

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106331 --- Comment #6 from H.J. Lu --- This is a latent bug. GCC 11 RTL expander generates: (insn 21 20 22 (set (mem/c:TI (reg:DI 92 [ D.3947 ]) [0 MEM [(void *)]+0 S16 A128]) (const_wide_int 0x20202020202020202020202020202020)) "x.f90":3:6

[PATCH] avr: Removed errant control characters

Signed-off-by: Joel Holdsworth --- gcc/config/avr/avr-devices.cc | 2 -- 1 file changed, 2 deletions(-) diff --git a/gcc/config/avr/avr-devices.cc b/gcc/config/avr/avr-devices.cc index aa284217f50..ff6a5441b77 100644 --- a/gcc/config/avr/avr-devices.cc +++ b/gcc/config/avr/avr-devices.cc @@

[Bug tree-optimization/106349] strlen reimplementation produces infinite loop with -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106349 Andrew Pinski changed: What|Removed |Added Resolution|--- |DUPLICATE

[Bug tree-optimization/102725] -fno-builtin leads to call of strlen since r12-4283-g6f966f06146be768

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102725 Andrew Pinski changed: What|Removed |Added CC||vincent.riviere at freesbee dot fr

[Bug c++/106348] c++modules: invalid syntax accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106348 Jonathan Wakely changed: What|Removed |Added Version|unknown |13.0 --- Comment #2 from Jonathan

[COMMITTED] tree-optimization/106280 - Check if transitives need to be registered.

Regardless of whether this is enough of an improvement for the PR, it should be done. Whenever a relation is registered with the oracle, it walks the dominator tree trying to apply any transitives it can find. FIrst, it should check whether the operands are already in any relation. If

[Bug c++/106348] c++modules: invalid syntax accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106348 --- Comment #1 from Ben Boeckel --- Forgot to mention: this occurs as of commit 63d182fb86e47323ac50d9368845d712e1f7da89

Re: [PATCH] c++: shortcut bad reference bindings [PR94894]

On 7/18/22 12:59, Patrick Palka wrote: In case of l/rvalue or cv-qual mismatch during reference binding, we try to give more helpful diagnostics by attempting a bad conversion that ignores the mismatch. But in doing so, we may end up instantiating an ill-formed conversion function, something

[PATCH] Fortran: error recovery on invalid array reference of non-array [PR103590]

Dear all, I intend to commit the attached patch as obvious to mainline within the next 24h unless someone complains. It replaces a lazy gfc_internal_error by an explicit error message and an error recovery path. As a side-effect, we now diagnose a previously missed error in testcase

[Bug fortran/103590] ICE: find_array_spec(): Missing spec

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103590 anlauf at gcc dot gnu.org changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot

[Bug c/106349] New: strlen reimplementation produces infinite loop with -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106349 Bug ID: 106349 Summary: strlen reimplementation produces infinite loop with -Os Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal

[Bug c++/106350] New: O3 memcpy warning when prepending a length-1 string literal to a constant std::string

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106350 Bug ID: 106350 Summary: O3 memcpy warning when prepending a length-1 string literal to a constant std::string Product: gcc Version: 13.0 Status: UNCONFIRMED

[Bug tree-optimization/106349] strlen reimplementation produces infinite loop with -Os

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106349 Andrew Pinski changed: What|Removed |Added Component|c |tree-optimization --- Comment #1 from

[Bug bootstrap/106172] Multiple ICEs building gcc-13 with gcc-12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106172 --- Comment #23 from Chris Clayton --- On 18/07/2022 19:13, aldyh at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106172 > > Aldy Hernandez changed: > >What|Removed |Added >

[Bug tree-optimization/106280] dom_oracle::register_transitives is expensive for deep dominator trees

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106280 --- Comment #2 from CVS Commits --- The master branch has been updated by Andrew Macleod : https://gcc.gnu.org/g:5e47c9333df6df1aa9da861f07e68f985d7d28fb commit r13-1737-g5e47c9333df6df1aa9da861f07e68f985d7d28fb Author: Andrew MacLeod Date:

[Bug c++/106348] New: c++modules: invalid syntax accepted

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106348 Bug ID: 106348 Summary: c++modules: invalid syntax accepted Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

RE: [PATCH] Add a heuristic for eliminate redundant load and store in inline pass.

Hi Honza, Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-July/597891.html Thanks, Lili. > -Original Message- > From: Gcc-patches On > Behalf Of Cui, Lili via Gcc-patches > Sent: Sunday, July 10, 2022 10:05 PM > To: Jan Hubicka > Cc: Lu, Hongjiu ; Liu, Hongtao > ;

[Bug libstdc++/106320] [10 regression] build failure (due to view requirement changes?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106320 --- Comment #3 from Martin Liška --- Started with r10-10808-g22b86cdc4d7fdd.

[Bug sanitizer/101978] thread sanitizer false positive when condition variable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101978 Boris Kolpackov changed: What|Removed |Added CC||boris at kolpackov dot net ---

[committed] arc: Fix interrupt's epilogue.

The stack pointer adjustment in interrupt epilogue is happening after restoring the ZOL registers which is wrong. Fixing this. gcc/ * config/arc/arc.cc (arc_expand_epilogue): Adjust the frame pointer first when in interrupts. gcc/testsuite/ *

[PATCH] xtensa: Correct the relative RTX cost that corresponds to the Move Immediate "MOVI" instruction

This patch corrects the overestimation of the relative cost of '(set (reg) (const_int N))' where N fits into the instruction itself. In fact, such overestimation confuses the RTL loop invariant motion pass. As a result, it brings almost no negative impact from the speed point of view, but

[Bug target/106340] flag set from SVE svwhilelt intrinsic not reused in loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106340 --- Comment #1 from Yichao Yu --- Also note that this is for code I've tweaked to match what the finally code as much as possible. For a complete implementation of this, I expect the loop transformation done for normal loop should move the

Re: [PATCH] match.pd: Add new abs pattern [PR94290]

Here's an updated version of the patch. Thanks -Sam On Thu, Jul 14, 2022 at 3:54 PM Andrew Pinski wrote: > On Thu, Jul 14, 2022 at 12:38 PM Sam Feifer wrote: > > > > > > > > On Thu, Jul 14, 2022 at 1:24 PM Andrew Pinski wrote: > >> > >> On Thu, Jul 14, 2022 at 7:09 AM Sam Feifer wrote: > >>

[Bug target/106324] ptrue not reused between vector instructions and predicate instructions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106324 --- Comment #3 from Yichao Yu --- Actually I just realized that the not instruction used the .d version as requested, the vector instruction didn’t….. I got it reversed in the original post……

Re: Re: [PATCH] libstdc++: Make __from_chars_alnum_to_val conversion explicit

(in reply to https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598412.html, adding libstdc++ to CC, with the same patch attached again) To clarify, this is not a fix for a user-facing issue of gcc or a fix for UB. It is just a minor UX improvement for developers that use the clang integer

Re: [PATCH] Simplify branching in algos

Hi     I just noticed that I still had this nice enhancement in my local branches.     Ok to commit ? François On 21/11/21 21:34, François Dumont wrote: A recent thread on this mailing list made me remember that this proposal is still open. I've updated it just to add a missing std

[Bug target/106253] [13 Regression] ICE in vect_transform_loops, at tree-vectorizer.cc:1032

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106253 rsandifo at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug sanitizer/64234] Statically sanitized executable does not export ASan symbols

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64234 Boris Kolpackov changed: What|Removed |Added CC||boris at kolpackov dot net ---

[Bug ipa/105682] [12/13 Regression] Both `-Wsuggest-attribute=pure` and `-Wsuggest-attribute=const` on same function since r12-5177-g494bdadf28d0fb35

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105682 --- Comment #6 from Jan Hubicka --- gcc-12.1.0 (bogus warning: `caller()` has no right to be const; it calls a pure function, and that function even contains inline assembly): I think the conlcusion here is correct. callee has pure attribute

[Bug target/106253] [13 Regression] ICE in vect_transform_loops, at tree-vectorizer.cc:1032

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106253 --- Comment #12 from CVS Commits --- The trunk branch has been updated by Richard Sandiford : https://gcc.gnu.org/g:7313381d2ce44b72b4c9f70bd5670e5d78d1f631 commit r13-1730-g7313381d2ce44b72b4c9f70bd5670e5d78d1f631 Author: Richard Sandiford

[PATCH] Fix builtin vs non-builtin partition merge in loop distribution

When r7-6373-g40b6bff965d004 fixed a costing issue it failed to make the logic symmetric which means that we now fuse normal vs. builtin when the cost model says so but we don't fuse builtin vs. normal. The following fixes that, also allowing the cost model to decide to fuse two builtin

[Bug c++/106341] New: Template argument deduction of template value parameter crashes compiler

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106341 Bug ID: 106341 Summary: Template argument deduction of template value parameter crashes compiler Product: gcc Version: 10.4.0 Status: UNCONFIRMED Severity:

[Bug c++/106337] Too many compilation errors generated with struct

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106337 Jonathan Wakely changed: What|Removed |Added Version|4.9.2 |13.0 Keywords|

RE: [PATCH] arm: Replace arm_builtin_vectorized_function [PR106253]

> -Original Message- > From: Richard Sandiford > Sent: Wednesday, July 13, 2022 9:14 AM > To: gcc-patches@gcc.gnu.org > Cc: Richard Earnshaw ; Kyrylo Tkachov > > Subject: [PATCH] arm: Replace arm_builtin_vectorized_function [PR106253] > > This patch extends the fix for PR106253 to

[PATCH] Improve common reduction vs builtin code generation in loop distribution

loop distribution currently cannot handle the situation when the last partition is a builtin but there's a common reduction in all partitions (like the final IV value). The following lifts this restriction by making the last non-builtin partition provide the definitions for the loop-closed PHI

[Bug target/106339] [13 Regression] ICE in exact_div, at poly-int.h:2232

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106339 Richard Biener changed: What|Removed |Added Target Milestone|--- |13.0

[committed 2/2] libgcc/arc: Update udivmodsi4 and make the lib safe for rf16

From: Claudiu Zissulescu The ARC soft udivmodsi4 algorithm and as well as using umodsi3 for reduced register set configurations are wrong. libgcc/ * config/arc/lib2funcs.c (udivmodsi4): Update AND mask. * config/arc/lib1funcs.S (umodsi3): Don't use it for RF16

[Bug target/106340] New: flag set from SVE svwhilelt intrinsic not reused in loop

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106340 Bug ID: 106340 Summary: flag set from SVE svwhilelt intrinsic not reused in loop Product: gcc Version: 12.1.0 Status: UNCONFIRMED Severity: normal

Re: [PATCH] ipa-cp: Fix assert triggering with -fno-toplevel-reorder (PR 106260)

> Hi, > > with -fno-toplevel-reorder (and -fwhole-program), there apparently can > be local functions without any callers. This is something that IPA-CP If there is possibility to trigger a local function without callers, I think one can also make two local functions calling each other but with

[Bug libstdc++/106320] [10 regression] build failure (due to view requirement changes?)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106320 --- Comment #4 from Jonathan Wakely --- The problem is that join_view still requires its _InnerView to be default-constructible, but that's a transform_view holding a non-default-constructible callable. For gcc-11 this isn't a problem because

Re: [PATCH] xtensa: Correct the relative RTX cost that corresponds to the Move Immediate "MOVI" instruction

On Mon, Jul 18, 2022 at 5:47 AM Takayuki 'January June' Suwa wrote: > > This patch corrects the overestimation of the relative cost of > '(set (reg) (const_int N))' where N fits into the instruction itself. > > In fact, such overestimation confuses the RTL loop invariant motion pass. > As a

[Bug fortran/106331] [12/13 Regression] Whole array assignment of empty string segfaults with -Og since r12-2633-ge5e164effa30fd2b

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106331 --- Comment #7 from H.J. Lu --- Breakpoint 6, expand_builtin_memset_args (dest=0x77b6f1a0, val=0x77f86978, len=0x77f86960, target=0x77da7400, mode=E_VOIDmode, orig_exp=0x77da9d38) at

[Bug target/83782] [10/11 Regression] Inconsistent address for hidden ifunc in a shared library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83782 Alexandre Oliva changed: What|Removed |Added CC||aoliva at gcc dot gnu.org --- Comment

[Bug target/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 Richard Earnshaw changed: What|Removed |Added CC||rguenth at gcc dot gnu.org ---

[committed] RISC-V/doc: Correct the name of `-mriscv-attribute'

Correct the name of the `-mriscv-attribute' invocation option, including a typo in the negated form. gcc/ * doc/invoke.texi (Option Summary): Fix `-mno-riscv-attribute'. (RISC-V Options): Likewise, and `-mriscv-attribute'. --- Hi, Verified with `make info pdf' and

[committed] RISC-V/doc: Correct the formatting of `-mstack-protector-guard-reg='

Add missing second space around the `-mstack-protector-guard-reg=' invocation option. gcc/ * doc/invoke.texi (Option Summary): Add missing second space around `-mstack-protector-guard-reg='. --- Hi, Verified with `make info pdf' and committed as obvious. Maciej ---

[Bug tree-optimization/106343] New: Addition with constants is not vectorized by SLP when it includes zero

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 Bug ID: 106343 Summary: Addition with constants is not vectorized by SLP when it includes zero Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords:

[committed] RISC-V/doc: Add index references for `mrelax' and `mriscv-attribute'

Add missing index references for the `-mrelax' and `-mriscv-attribute' invocation options. gcc/ * doc/invoke.texi (RISC-V Options): Add index references for `mrelax' and `mriscv-attribute'. --- Hi, Verified with `make info pdf' and committed as obvious. Maciej ---

[Bug tree-optimization/106343] SLP does not support no-op case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 Andrew Pinski changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1

[Bug tree-optimization/106343] SLP does not support no-op case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 Andrew Pinski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug tree-optimization/106343] SLP does not support no-op case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 --- Comment #3 from Andrew Pinski --- I should note that I noticed LLVM does not handle this either. Basically the following operators and values can be used: For integer: + 0 - 0 * 1 / 1 | 0 & -1 (all ones) ^ 0 For floating point (only with

[PATCH] RISC-V: Add RTX costs for `if_then_else' expressions

Fix a performance regression from commit 391500af1932 ("Do not ignore costs of jump insns in combine."), a part of the m68k series for MODE_CC conversion (), observed in soft-fp code in libgcc used by some of the embench-iot benchmarks.

[Bug tree-optimization/106343] SLP does not support no-op case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 Erick Ochoa changed: What|Removed |Added CC||eochoa at gcc dot gnu.org --- Comment #5

[Bug tree-optimization/106343] SLP does not support no-op case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 --- Comment #4 from Andrew Pinski --- (In reply to Andrew Pinski from comment #3) > I should note that I noticed LLVM does not handle this either. > > Basically the following operators and values can be used: > For integer: > + 0 > - 0 > * 1 >

[PATCH] c++: shortcut bad reference bindings [PR94894]

In case of l/rvalue or cv-qual mismatch during reference binding, we try to give more helpful diagnostics by attempting a bad conversion that ignores the mismatch. But in doing so, we may end up instantiating an ill-formed conversion function, something that would otherwise be avoided if we

Re: [PATCH] match.pd: Add new abs pattern [PR94290]

Just realized I had mixed up the 9 and the 2 when labelling the patch. This patch is referring to pr94920 not pr94290. Attached is a fixed patch file. Sorry for any confusion. On Mon, Jul 18, 2022 at 9:07 AM Sam Feifer wrote: > Here's an updated version of the patch. > > Thanks > -Sam > > On

[Bug target/106342] [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106342 Marek Polacek changed: What|Removed |Added Target Milestone|--- |12.2 Target|

[Bug target/106342] New: [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106342 Bug ID: 106342 Summary: [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity:

[Bug fortran/106336] BLOCK construct and host association are not handled correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106336 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug bootstrap/106172] Multiple ICEs building gcc-13 with gcc-12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106172 --- Comment #22 from Andrew Pinski --- (In reply to Aldy Hernandez from comment #21) > Confirmed on x86-64 with: ./configure --enable-languages=c,c++ > --enable-checking=no. > > Interestingly, --enable-checking=release works. well some

[Bug target/106347] New: [13 Regression] ICE in ix86_output_ssemov, at config/i386/i386.cc:5565, or ICE in final_scan_insn_1, at final.cc:2860 (error: could not split insn)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106347 Bug ID: 106347 Summary: [13 Regression] ICE in ix86_output_ssemov, at config/i386/i386.cc:5565, or ICE in final_scan_insn_1, at final.cc:2860 (error: could not split insn)

[Bug testsuite/106344] New: A few x86_64 tests fail with -march=x86-64-v2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106344 Bug ID: 106344 Summary: A few x86_64 tests fail with -march=x86-64-v2 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug rtl-optimization/106210] [10/11/12/13 Regression] missing shrink wrap for simple case since r9-3594-g8d2d39587d941a40

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106210 --- Comment #6 from Segher Boessenkool --- The prepare_shrink_wrap code handles only very limited very simple cases. After g:8d2d39587d94 there is another copy at this point (which is an *improvement*, it gives more freedom). I don't see how

[Bug bootstrap/106172] Multiple ICEs building gcc-13 with gcc-12

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106172 Aldy Hernandez changed: What|Removed |Added CC||aldyh at gcc dot gnu.org

[Bug target/106342] [12/13 Regression] internal compiler error: in extract_insn, at recog.cc:2791

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106342 --- Comment #1 from Marek Polacek --- gcc.dg/vect/fast-math-vect-call-1.c also ICEs like that.

[PING][PATCH v2] RISC-V: Split unordered FP comparisons into individual RTL insns

On Mon, 4 Jul 2022, Maciej W. Rozycki wrote: > These instructions are only produced via an expander already, so change > the expander to emit individual RTL insns for each machine instruction > in the ultimate ultimate sequence produced rather than deferring to a > single RTL insn producing

[Bug target/106187] armhf: Miscompilation at O2 level (O0 / O1 are working)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106187 --- Comment #27 from Richard Earnshaw --- BTW, compile flags for an arm-none-eabi compiler are: cc1plus -march=armv7-a+fp -mfloat-abi=hard -O2 -quiet -mthumb -fno-short-enums -fno-exceptions -fvisibility-inlines-hidden -fmath-errno

[Bug tree-optimization/106343] Addition with constants is not vectorized by SLP when it includes zero

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 ktkachov at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

Re: [PATCH] ipa-cp: Fix assert triggering with -fno-toplevel-reorder (PR 106260)

Hi, On Mon, Jul 18 2022, Jan Hubicka wrote: >> Hi, >> >> with -fno-toplevel-reorder (and -fwhole-program), there apparently can >> be local functions without any callers. This is something that IPA-CP > > If there is possibility to trigger a local function without callers, I > think one can

[Bug tree-optimization/106343] SLP does not support no-op case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106343 --- Comment #6 from Andrew Pinski --- (In reply to Erick Ochoa from comment #5) > I think it should be possible to also consider the bit-shifts operations: > > >> 0 > << 0 Yes and rotates too.

[Bug testsuite/106345] New: Some ppc64le tests fail with -mcpu=power9 -mtune=power9

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106345 Bug ID: 106345 Summary: Some ppc64le tests fail with -mcpu=power9 -mtune=power9 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug tree-optimization/106346] New: Potential regression on vectorization of left shift with constants

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106346 Bug ID: 106346 Summary: Potential regression on vectorization of left shift with constants Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords:

  1   2   >