On Mon, May 2, 2022 at 8:34 AM Richard Biener
wrote:
>
> On Sun, May 1, 2022 at 2:15 PM Aldy Hernandez via Gcc-patches
> wrote:
> >
> > We are ICEing in set_range_info_raw because value_range_kind cannot be
> > VR_VARYING, since SSA_NAME_RANGE_TYPE can only hold VR_RANGE /
> > VR_ANTI_RANGE. Mos
On Tue, Apr 26, 2022 at 04:40:33PM +0200, Hans-Peter Nilsson wrote:
> > From: Thomas Koenig via Gcc-patches
> > Date: Fri, 22 Apr 2022 15:59:45 +0200
>
> > Hi Mikael,
> >
> > > Ping for the four patches starting at
> > > https://gcc.gnu.org/pipermail/fortran/2022-April/057759.html :
> > > https
On Mon, May 2, 2022 at 8:30 AM Richard Biener
wrote:
>
> On Fri, Apr 29, 2022 at 6:22 PM Aldy Hernandez wrote:
> >
> > On Fri, Apr 29, 2022 at 12:13 PM Richard Biener
> > wrote:
> > >
> > > On Fri, Apr 29, 2022 at 11:53 AM Aldy Hernandez wrote:
> > > >
> > > > On Fri, Apr 29, 2022 at 9:09 AM Ri
That supports skipping of an object file (LDPS_NO_SYMS). The API will be used
by mold
and is there for some time in linkers.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
lto-plugin/ChangeLog:
* lto-plugin.c (struct plugin_
Hi.
This in a new plug-in function that helps identifying compiler
by a linker. Will be used in mold linker.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
include/ChangeLog:
* plugin-api.h (enum ld_plugin_compiler): New enu
On 3/31/22 09:01, Martin Liška wrote:
> @Jakub: May I install it once stage1 opens?
May I please ping this?
Thanks,
Martin
>
> Cheers,
> Martin
>
> On 1/3/22 12:43, Martin Liška wrote:
>> PING: Jakub?
>>
>> On 12/15/21 10:57, Martin Liška wrote:
>>> On 12/14/21 17:12, Jakub Jelinek wrote:
On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
>
> Hi.
>
> This in a new plug-in function that helps identifying compiler
> by a linker. Will be used in mold linker.
>
> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>
> Ready to be installed?
It looks a bit backward t
On 5/2/22 10:09, Richard Biener wrote:
> On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
>>
>> Hi.
>>
>> This in a new plug-in function that helps identifying compiler
>> by a linker. Will be used in mold linker.
>>
>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>>
>>
On Fri, Apr 29, 2022 at 01:23:46PM +0200, Richard Biener wrote:
> On Fri, 29 Apr 2022, Jakub Jelinek wrote:
>
> > On Fri, Apr 29, 2022 at 01:11:31PM +0200, Jakub Jelinek via Gcc-patches
> > wrote:
> > > Depends. DECL_IN_CONSTANT_POOL decls can appear 2 ways, through
> > > tree_output_constant_de
On Mon, 2 May 2022, Jakub Jelinek wrote:
> On Fri, Apr 29, 2022 at 01:23:46PM +0200, Richard Biener wrote:
> > On Fri, 29 Apr 2022, Jakub Jelinek wrote:
> >
> > > On Fri, Apr 29, 2022 at 01:11:31PM +0200, Jakub Jelinek via Gcc-patches
> > > wrote:
> > > > Depends. DECL_IN_CONSTANT_POOL decls ca
This patch fixes an issue introduced by commit
ef9a53feae5701953da9161afef2aea0329ec8b2:
gcc --coverage main.c && ./a.out
libgcov profiling error:a-main.gcda:Error writing
gcc/ChangeLog:
* gcov-io.cc (gcov_rewrite): Clear the file error status.
---
gcc/gcov-io.cc | 5 -
1 file chan
We have to watch out for vectorized stmt insert locations if the
def from the last stmt alters control flow. We constrain region
building so we know the def is outside of the current region
and thus we can insert at the region start point.
Bootstrapped and tested on x86_64-unknown-linux-gnu, push
On 5/2/22 10:43, Sebastian Huber wrote:
> This patch fixes an issue introduced by commit
> ef9a53feae5701953da9161afef2aea0329ec8b2:
Works for me, please install it.
Martin
>
> gcc --coverage main.c && ./a.out
> libgcov profiling error:a-main.gcda:Error writing
>
> gcc/ChangeLog:
>
> *
Hi,
I'd like to ping this patch on behalf of Artem.
Alexander
On Sun, 17 Apr 2022, Artem Klimov wrote:
> Fix issue PR99619, which asks to optimize TLS access based on
> visibility. The fix is implemented as an IPA optimization, which allows
> to take optimized visibility status into account (as
On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
>
> On 5/2/22 10:09, Richard Biener wrote:
> > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
> >>
> >> Hi.
> >>
> >> This in a new plug-in function that helps identifying compiler
> >> by a linker. Will be used in mold linker.
> >>
> >> Pat
On Mon, May 2, 2022 at 10:51 AM Richard Biener
wrote:
>
> On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
> >
> > On 5/2/22 10:09, Richard Biener wrote:
> > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
> > >>
> > >> Hi.
> > >>
> > >> This in a new plug-in function that helps identify
On 5/2/22 10:51, Richard Biener wrote:
> On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
>>
>> On 5/2/22 10:09, Richard Biener wrote:
>>> On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
Hi.
This in a new plug-in function that helps identifying compiler
by a linker.
On Mon, May 2, 2022 at 10:54 AM Richard Biener
wrote:
>
> On Mon, May 2, 2022 at 10:51 AM Richard Biener
> wrote:
> >
> > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
> > >
> > > On 5/2/22 10:09, Richard Biener wrote:
> > > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
> > > >>
>
On Mon, May 2, 2022 at 10:57 AM Martin Liška wrote:
>
> On 5/2/22 10:51, Richard Biener wrote:
> > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
> >>
> >> On 5/2/22 10:09, Richard Biener wrote:
> >>> On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
>
> Hi.
>
> This in
On Mon, May 2, 2022 at 11:00 AM Richard Biener
wrote:
>
> On Mon, May 2, 2022 at 10:57 AM Martin Liška wrote:
> >
> > On 5/2/22 10:51, Richard Biener wrote:
> > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
> > >>
> > >> On 5/2/22 10:09, Richard Biener wrote:
> > >>> On Mon, May 2, 2022
On 5/2/22 11:00, Richard Biener wrote:
> On Mon, May 2, 2022 at 10:57 AM Martin Liška wrote:
>>
>> On 5/2/22 10:51, Richard Biener wrote:
>>> On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
On 5/2/22 10:09, Richard Biener wrote:
> On Mon, May 2, 2022 at 9:52 AM Martin Liška wro
> On Mon, May 2, 2022 at 10:51 AM Richard Biener
> wrote:
> >
> > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
> > >
> > > On 5/2/22 10:09, Richard Biener wrote:
> > > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
> > > >>
> > > >> Hi.
> > > >>
> > > >> This in a new plug-in functi
On 5/2/22 11:03, Richard Biener wrote:
> In fact I think GCC is correct in its handling and LLVM would need to dup ()
> the
> file descriptor. Was this issue raised with the LLVM folks?
I don't know here.
> I suspect the BFD
> linker will also not work with LLVM due to this?
I'm not sure BFD i
On Mon, May 2, 2022 at 11:06 AM Jan Hubicka wrote:
>
> > On Mon, May 2, 2022 at 10:51 AM Richard Biener
> > wrote:
> > >
> > > On Mon, May 2, 2022 at 10:19 AM Martin Liška wrote:
> > > >
> > > > On 5/2/22 10:09, Richard Biener wrote:
> > > > > On Mon, May 2, 2022 at 9:52 AM Martin Liška wrote:
On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote:
>
> On 5/2/22 11:03, Richard Biener wrote:
> > In fact I think GCC is correct in its handling and LLVM would need to dup
> > () the
> > file descriptor. Was this issue raised with the LLVM folks?
>
> I don't know here.
>
> > I suspect the BFD
>
On 5/2/22 11:14, Richard Biener wrote:
> On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote:
>>
>> On 5/2/22 11:03, Richard Biener wrote:
>>> In fact I think GCC is correct in its handling and LLVM would need to dup
>>> () the
>>> file descriptor. Was this issue raised with the LLVM folks?
>>
>>
On Mon, May 2, 2022 at 11:27 AM Martin Liška wrote:
>
> On 5/2/22 11:14, Richard Biener wrote:
> > On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote:
> >>
> >> On 5/2/22 11:03, Richard Biener wrote:
> >>> In fact I think GCC is correct in its handling and LLVM would need to dup
> >>> () the
> >
On Mon, May 2, 2022 at 11:36 AM Richard Biener
wrote:
>
> On Mon, May 2, 2022 at 11:27 AM Martin Liška wrote:
> >
> > On 5/2/22 11:14, Richard Biener wrote:
> > > On Mon, May 2, 2022 at 11:08 AM Martin Liška wrote:
> > >>
> > >> On 5/2/22 11:03, Richard Biener wrote:
> > >>> In fact I think GCC
On 5/2/22 11:36, Richard Biener wrote:
> Linkers will need heuristics anyway for older plugins and I think
> LLVM could just behave here.
Leaving that for the future, I may return to it. Right now, the benefit
is pretty low to me.
Martin
Hi!
On the following testcase, we emit deprecated warnings or unavailable errors
even on merge declarations of those lambdas (the dg-bogus directives), while
IMHO we should emit them only when something actually calls those lambdas.
The following patch temporarily disables that diagnostics during
The following extends SLP discovery to handle swapped operands
in comparisons.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
2022-05-02 Richard Biener
PR tree-optimization/104240
* tree-vect-slp.cc (op1_op0_map): New.
(vect_get_operand_map): Handle compa
On Wed, Apr 20, 2022 at 8:35 PM Roger Sayle wrote:
>
>
> This patch implements the constant folding optimization(s) described in
> PR middle-end/98865, which should help address the serious performance
> regression of Botan AES-128/XTS mentioned in PR tree-optimization/98856.
> This combines aspec
On Tue, Feb 1, 2022 at 9:57 AM Roger Sayle wrote:
>
>
> This patch fixes PR tree-optimization/102950, which is a P2 regression,
> by providing better range bounds for BIT_XOR_EXPR, BIT_AND_EXPR and
> BIT_IOR_EXPR on signed integer types. In general terms, any binary
> bitwise operation on sign-ex
This makes sure to not consider calls to builtin decls with
mismatching arguments as inexpensive.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
2022-04-13 Richard Biener
* tree-scalar-evolution.cc (expression_expensive_p):
Never consider mismatched calls as chea
Hi!
On 2022-05-01T11:02:29+0100, Iain Sandoe via Gcc wrote:
>> On 29 Apr 2022, at 15:34, Jakub Jelinek via Gcc wrote:
>>
>> The first release candidate for GCC 12.1 is available from
>>
>> https://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-20220429/
>> ftp://gcc.gnu.org/pub/gcc/snapshots/12.1.0-RC-
Hello,
On Sun, Apr 17 2022, Artem Klimov via Gcc-patches wrote:
> Fix issue PR99619, which asks to optimize TLS access based on
> visibility. The fix is implemented as an IPA optimization, which allows
> to take optimized visibility status into account (as well as avoid
> modifying all language fr
Consider
struct F {
F(int) {}
F operator()(int) const { return *this; }
};
and
F(i)(0)(0);
where we're supposed to first call the constructor and then invoke
the operator() twice. However, we parse this as an init-declarator:
"(i)" looks like a perfectly valid declarator, then we
This patch fixes an oversight whereby we treated >= as the end of
a template argument. This causes problems in C++14, because in
cp_parser_template_argument we go different ways for C++14 and C++17:
/* It must be a non-type argument. In C++17 any constant-expression is
allowed. */
if (
On Mon, 2 May 2022, Martin Jambor wrote:
> > Co-Authored-By: Alexander Monakov
>
> (Minor nit and I don't care too much, but in GCC we traditionally
> specify co-authors in the ChangeLog entry beginning by providing more
> names, one per line. But perhaps we want to adapt more widely used
> p
Pinging this series again.
Link: https://gcc.gnu.org/pipermail/gcc-patches/2022-April/592685.html
This series adds new C-family frontend attributes for recording string
"tags" in DWARF and BTF debug info to support kernel use cases.
There remains one issue in the implementation which has not b
On Fri, Apr 29, 2022 at 10:38 AM H.J. Lu wrote:
>
> Add .note.GNU-stack assembly source to avoid linker warning:
>
> ld: warning: /tmp/ccPZSZ7Z.o: missing .note.GNU-stack section implies
> executable stack
> ld: NOTE: This behaviour is deprecated and will be removed in a future
> version of the
Currently when checking the constraints of a class template, we do so in
the context of the template, not the specialized type. This is the best
we can do for a primary template since the specialized type is valid
only if the primary template's constraints are satisfied. But for a
partial special
On 5/2/22 18:04, Martin Jambor wrote:
> (Minor nit and I don't care too much, but in GCC we traditionally
> specify co-authors in the ChangeLog entry beginning by providing more
> names, one per line. But perhaps we want to adapt more widely used
> practices.)
Hello.
Using Co-Authored-By is fine
While looking at PR96645 I noticed that while we were diagnosing names
changing meaning in the full class context, we weren't doing this for
lookups in nested class bodies.
Note that this breaks current range-v3; I've submitted a pull request to fix
its violation of the rule.
Tested x86_64-pc-lin
Hi!
On Thu, Apr 28, 2022 at 10:53:40PM -0300, Alexandre Oliva wrote:
> On Apr 28, 2022, Segher Boessenkool wrote:
> > On Thu, Apr 28, 2022 at 03:09:54AM -0300, Alexandre Oliva wrote:
> >> +"no __intrinsic_type support for [long] double on PPC w/o
> >> VSX");
> > This change isn't in
On PR102629 I noticed that we were giving the entire lambda as the location
for this template-id.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog:
* pt.cc (tsubst_copy_and_build) [TEMPLATE_ID_EXPR]: Copy location.
(do_auto_deduction): Use expr location.
gcc/tests
Ping #5:
| Date: Tue, 12 Apr 2022 21:14:55 -0400
| From: Michael Meissner
| Subject: [PATCH, V4] Eliminate power8 fusion options, use power8 tuning, PR
target/102059
| Message-ID:
https://gcc.gnu.org/pipermail/gcc-patches/2022-April/593153.html
We really need closure on this so I can do the b
On May 2, 2022, Segher Boessenkool wrote:
> Send full patches always please.
I'll try to remember that. In case I fail, I hope you won't mind too
much reminding me.
(You'd also asked me not to send patches as followups, but... revised
versions of a patch still belong in the same thread, righ
On Apr 28, 2022, Richard Biener wrote:
> On Thu, 28 Apr 2022, Alexandre Oliva wrote:
>>
>> gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c covers ppc variants
>> that accept and reject misaligned accesses. The message that it
>> expects for rejection was removed in the gcc-11 development cycle b
The floating-point overloads of from_char are only declared if
_GLIBCXX_HAVE_USELOCALE is #defined as nonzero. That's exposed from
charconv as _cpp_lib_to_chars >= 201611L, so guard the test body with
that.
Regstrapped on ppc64le-linux-gnu, and tested on
x86_64-linux-gnu-x-ppc{,64}-vx7r2 (witho
vec-mul is an execution test, but it only requires a powerpc_vsx_ok
effective target, which is enough only for compile tests. In order to
To check for runtime and execution environment support, we need to
require vsx_hw. Make that a condition for execution, but still
perform a compile test if t
On Mon, 2 May 2022, Alexandre Oliva wrote:
> On Apr 28, 2022, Richard Biener wrote:
>
> > On Thu, 28 Apr 2022, Alexandre Oliva wrote:
> >>
> >> gcc.dg/vect/costmodel/ppc/costmodel-vect-31a.c covers ppc variants
> >> that accept and reject misaligned accesses. The message that it
> >> expects f
52 matches
Mail list logo
