Hi Harald,
This is fine for mainline and for backporting if you feel so inclined.
Thanks for the patch.
Paul
On Mon, 16 Jan 2023 at 21:12, Harald Anlauf via Fortran
wrote:
> Dear all,
>
> it appears that the fix for pr107874 uncovered a latent bug
> for the case of arrays of type character
On Sat, 21 Jan 2023, Jan Hubicka wrote:
> > When we have a static declaration without definition we diagnose
> > that and turn it into an extern declaration. That can alter
> > the outcome of maybe_special_function_p here and there's really
> > no point in doing that, so don't.
> >
> >
On Fri, 20 Jan 2023, NightStrike wrote:
> On Fri, Jan 20, 2023 at 1:40 PM Gaius Mulley via Gcc-patches
> wrote:
> >
> > Richard Biener writes:
> >
> > > The following adjusts libgm2 to properly use the multilib build
> > > infrastructure, thereby fixing the install with
> > >
On Tue, Jan 17, 2023 at 6:05 PM Iain Sandoe via Gcc-patches
wrote:
>
> Tested on x86_64-linux-gnu (with a 32b multilib), powerpc, i686 and
> x86_64-darwin. OK for trunk?
Reading through the patch I fear there's more issues lurking
(-sysroot?) but this seems to be
a step in the right direction,
libstdc++: [_GLIBCXX_DEBUG] Remove useless constructor checks
Creating a safe iterator from a normal iterator is done within the
library where we
already know that it is done correctly. The rare situation where a
user would use safe
iterators for his own purpose is non-Standard
On 2023/01/23 0:45, Max Filippov wrote:
> On Fri, Jan 20, 2023 at 8:39 PM Takayuki 'January June' Suwa
> wrote:
>> On 2023/01/21 0:14, Max Filippov wrote:
>>> After having this many attempts and getting to the issues that are
>>> really hard to detect I wonder if the target backend is the right
Arsen Arsenović writes:
> ---
> Evening,
>
> I've gone through lists.html and documented the Sourceware public-inbox
> instance, since it seems to be commonly missed, yet some might find useful.
>
> This patch includes:
> - A brief summary of what the public-inbox provides,
> - A brief
---
Evening,
I've gone through lists.html and documented the Sourceware public-inbox
instance, since it seems to be commonly missed, yet some might find useful.
This patch includes:
- A brief summary of what the public-inbox provides,
- A brief summary on alternative methods of accessing the
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
This PR points out a case where we are not extending the lifetime of a
temporary when the subobject is denoted by a pointer-to-member operation.
These rules were clarified in C++20 by CWG1299.
There are other cases that also need to be
On 1/22/23 15:50, Jakub Jelinek wrote:
On Sun, Jan 22, 2023 at 03:40:26PM -0500, Jason Merrill wrote:
2023-01-21 Jakub Jelinek
PR c++/108474
* cp-gimplify.cc (cp_fold_r): Handle structured bindings
vars like anon union artificial vars.
*
On Sun, Jan 22, 2023 at 03:40:26PM -0500, Jason Merrill wrote:
> > 2023-01-21 Jakub Jelinek
> >
> > PR c++/108474
> > * cp-gimplify.cc (cp_fold_r): Handle structured bindings
> > vars like anon union artificial vars.
> >
> > * g++.dg/cpp1z/decomp57.C: New test.
> > *
On 1/21/23 04:59, Jakub Jelinek wrote:
Hi!
As reported by Andrew Pinski, structured bindings (with the exception
of the ones using std::tuple_{size,element} and get which are really
standalone variables in addition to the binding one) also use
DECL_VALUE_EXPR and needs the same treatment in
The recent gcc.dg/tree-ssa/clz-char.c test case failed for PRU target,
exposing a wrong code generation bug in the PRU backend. The "clz"
pattern did not produce correct output for QI and HI input operand
modes. SI mode is ok.
The "clz" pattern is expanded to an LMBD instruction to get the
Ping!
Am 16.01.23 um 22:11 schrieb Harald Anlauf via Gcc-patches:
Dear all,
it appears that the fix for pr107874 uncovered a latent bug
for the case of arrays of type character and size zero when
passed to the intrinsics MERGE and SPREAD as SOURCE. In that
case, there is no constructor from
On 1/17/23 19:50, juzhe.zh...@rivai.ai wrote:
From: Ju-Zhe Zhong
Since LCM will destroy CFG, we are going to reorder the location of VSETVL PASS
at least before bbro (block-reorder PASS) which is before split3 PASS. We need
to call it in VSETVL PASS to get final RVV instructions patterns.
On 1/17/23 19:53, juzhe.zh...@rivai.ai wrote:
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vsetvl.cc (pass_vsetvl::done): Remove DCE.
* config/riscv/t-riscv: Ditto.
OK. Presumably this is because the pass is now placed before DCE.
Jeff
On 1/17/23 19:58, juzhe.zh...@rivai.ai wrote:
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vsetvl.cc: Clang-format.
OK.
jeff
On 1/17/23 20:03, juzhe.zh...@rivai.ai wrote:
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-passes.def (INSERT_PASS_BEFORE): Reorder VSETVL
PASS.
It'd be useful to know the motivation here, I could easily see someone
in the future finding a case where the location of
On 1/17/23 20:06, juzhe.zh...@rivai.ai wrote:
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-vsetvl.h: Change it into public.
OK.
jeff
On 1/17/23 20:16, juzhe.zh...@rivai.ai wrote:
From: Ju-Zhe Zhong
Since we have same function in class and static function calling get_avl.
Adding :: to avoid codes confusing.
gcc/ChangeLog:
* config/riscv/riscv-vsetvl.cc
(pass_vsetvl::get_backward_fusion_type): Add ::.
Is there
On 1/20/23 02:33, juzhe.zh...@rivai.ai wrote:
From: Ju-Zhe Zhong
According to RVV ISA, RVV doesn't support EEW == 64 vector type for zve32x
and zve32f. So it makes sense add predicate in the iterators of EEW = 64
vector modes.
gcc/ChangeLog:
* config/riscv/vector-iterators.md:
On 12/7/22 08:45, Cupertino Miranda wrote:
On 12/2/22 10:52, Cupertino Miranda via Gcc-patches wrote:
This commit is a follow up of bugzilla #107181.
The commit /a0aafbc/ changed the default implementation of the
SELECT_SECTION hook in order to match clang/llvm behaviour w.r.t the
On 1/9/23 00:57, Richard Biener wrote:
On Mon, Dec 5, 2022 at 7:07 PM Jeff Law via Gcc-patches
wrote:
On 12/2/22 10:52, Cupertino Miranda via Gcc-patches wrote:
Changed target code to select .rodata section for 'const volatile'
defined variables.
This change is in the context of the
On 1/19/23 02:59, Cupertino Miranda wrote:
Hi Jeff,
Kindly calling your attention to this thread.
Sorry, just crazy busy around here.
Jeff
Iain Sandoe writes:
> tested on x86_64-darwin21 with an updated compiler that does not support
> the path concatentation and on an unpatched trunk.
> OK for trunk?
> thanks
> Iain
>
> --- 8< ---
>
> The original implementation for Modula-2 search paths allows things like
> '-I/path/a:/path/b'.
tested on x86_64-darwin21 with an updated compiler that does not support
the path concatentation and on an unpatched trunk.
OK for trunk?
thanks
Iain
--- 8< ---
The original implementation for Modula-2 search paths allows things like
'-I/path/a:/path/b'. Such paths are not compatible with the
On 1/22/23 5:38 AM, Mikael Morin wrote:
Hello,
Le 22/01/2023 à 00:59, Jerry D via Fortran a écrit :
(...)
Proposed ChangeLog entry using git gcc-commit-mklog:
Author: Jerry DeLisle
Date: Sat Jan 21 15:47:19 2023 -0800
Revise the line end tests to pass on certain windows test
On Fri, Jan 20, 2023 at 8:39 PM Takayuki 'January June' Suwa
wrote:
> On 2023/01/21 0:14, Max Filippov wrote:
> > After having this many attempts and getting to the issues that are
> > really hard to detect I wonder if the target backend is the right place
> > for this optimization?
> >
> I guess
Hello,
Le 22/01/2023 à 00:59, Jerry D via Fortran a écrit :
(...)
Proposed ChangeLog entry using git gcc-commit-mklog:
Author: Jerry DeLisle
Date: Sat Jan 21 15:47:19 2023 -0800
Revise the line end tests to pass on certain windows test environments
which inject spurious /r
I missed this originally and noticed looking for something else.
Pushed.
Gerald
---
htdocs/gcc-10/changes.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 2bad8ea3..4acc8d12 100644
---
Hi Rainer,
> On 22 Jan 2023, at 09:44, Rainer Orth wrote:
>
>> Tested on i686, powerpc, x86_64, Arm64 Darwin, x86_64-linux-gnu,
>> pushed to trunk, thanks,
>> Iain
>>
>> --- 8< ---
>>
>> For several Darwin linker versions, the link paths are first traversed
>> looking for shared libraries,
Hi Iain,
> Tested on i686, powerpc, x86_64, Arm64 Darwin, x86_64-linux-gnu,
> pushed to trunk, thanks,
> Iain
>
> --- 8< ---
>
> For several Darwin linker versions, the link paths are first traversed
> looking for shared libraries, and then again looking for archives.
>
> We want the paths to be
Tested on i686, powerpc, x86_64, Arm64 Darwin, x86_64-linux-gnu,
pushed to trunk, thanks,
Iain
--- 8< ---
For several Darwin linker versions, the link paths are first traversed
looking for shared libraries, and then again looking for archives.
We want the paths to be searched for both shared
33 matches
Mail list logo
