Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the German team of translators. The file is available at:
https://translationproject.org/latest/gcc/de.po
(This file,
Hi,
This Patch contains the function that gets all global ICVs information,
and prototypes of local ICVs.
Notes:
1) gomp_affinity_format_len doesn't have a value so I assumed that
gomp_affinity_format has length 100 for now.
2) I didn't have any knowledge in OpenMP before this project,
so if
On 2/11/22 14:55, Jakub Jelinek wrote:
Hi!
As mentioned by Jason in the PR, non-trivially-copyable types (or non-POD
for purposes of layout?) types can be base classes of derived classes in
which the padding in those non-trivially-copyable types can be redused for
some real data members or even
On 2/21/22 04:25, Jakub Jelinek wrote:
Hi!
The new expression constant expression evaluation right now tries to
deduce how many elts the array it uses for the heap or heap [] vars
should have (or how many elts should its trailing array have if it has
cookie at the start). As new is lowered at
On Fri, Mar 11, 2022 at 3:55 PM Joseph Myers wrote:
>
> On Fri, 11 Mar 2022, Krishna Narayanan via Gcc-patches wrote:
>
> > Hello,
> > The following is a patch for the PR92209,which gives a warning when
> > the function prototype does not specify its argument type.In this
> > patch there has been
On 3/10/22 11:27, Patrick Palka wrote:
On Wed, 9 Mar 2022, Jason Merrill wrote:
On 3/1/22 18:08, Patrick Palka wrote:
A well-formed call to std::move/forward is equivalent to a cast, but the
former being a function call means it comes with bloated debug info, which
persists even after the
On Fri, Mar 11, 2022 at 03:07:39PM -0600, Segher Boessenkool wrote:
> On Fri, Mar 11, 2022 at 09:57:50PM +0100, Jakub Jelinek wrote:
> > On Fri, Mar 11, 2022 at 02:51:23PM -0600, Segher Boessenkool wrote:
> > > On Fri, Mar 11, 2022 at 08:42:27PM +, Joseph Myers wrote:
> > > > The version of
On 3/10/22 12:41, Patrick Palka wrote:
On Wed, 9 Mar 2022, Jason Merrill wrote:
On 3/9/22 10:39, Patrick Palka wrote:
On Tue, 8 Mar 2022, Jason Merrill wrote:
On 3/2/22 14:32, Patrick Palka wrote:
In order to be able to perform CTAD for a dependently-scoped template
such as A::B in the
This patch resolves PR tree-optimization/101895 a missed optimization
regression, by adding a constant folding simplification to match.pd to
simplify the transform "mult; vec_perm; plus" into "vec_perm; mult; plus"
with the aim that keeping the multiplication and addition next to each
other
On 3/10/22 18:04, Marek Polacek wrote:
Since r9-6073 cxx_eval_store_expression preevaluates the value to
be stored, and that revealed a crash where a template code (here,
code=IMPLICIT_CONV_EXPR) leaks into cxx_eval*.
It happens because we're performing build_vec_init while processing
a
On 3/10/22 15:30, Patrick Palka wrote:
When shortcutting bad conversions during overload resolution, we assume
argument conversions get computed in sequential order and that therefore
we just need to inspect the last conversion in order to determine if _any_
conversion is missing. But this
Just following server redirects - http to https.
Pushed.
Gerald
---
htdocs/projects/sched-treegion.html | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/htdocs/projects/sched-treegion.html
b/htdocs/projects/sched-treegion.html
index d421d87b..d5cefa03 100644
---
I doubt anyone is using the GCC 5 release notes to get to that page,
and the link broke without a proper redirect, so make it a textual
reference (only).
Pushed.
Gerald
---
htdocs/gcc-5/changes.html | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/htdocs/gcc-5/changes.html
On Fri, Mar 11, 2022 at 02:51:23PM -0600, Segher Boessenkool wrote:
> On Fri, Mar 11, 2022 at 08:42:27PM +, Joseph Myers wrote:
> > The version of this patch applied to GCC 10 branch (commit
> > 641b407763ecfee5d4ac86d8ffe9eb1eeea5fd10) has broken the glibc build for
> >
On Fri, Mar 11, 2022 at 02:41:05PM -0600, Segher Boessenkool wrote:
> On Fri, Mar 11, 2022 at 01:07:29AM -0500, Michael Meissner wrote:
> > Fix DImode to TImode sign extend issue, PR target/104898
>
> > When I wrote the extendditi2 pattern, I forgot that mtvsrdd had that
> > behavior so I used a
Hi,
This patch addresses comments made in PR104552 about documented D
language options.
Bootstrapped and committed to mainline.
Regards,
Iain.
---
gcc/d/ChangeLog:
PR translation/104552
* lang.opt (fdump-cxx-spec=): Fix typo in argument handle.
(fpreview=fixaliasthis):
Hi,
This patch refactors the ImportVisitor to cache the generated result
decl in a hash_map. Originally, these were cached in the front-end AST
node field `isym'. However, this field is soon to be removed.
Bootstrapped and regression tested on x86_64-linux-gnu/m32/mx32, and
committed to
On Linux/x86_64,
251ea6dfbdb4448875e41081682bb3aa451b5729 is the first bad commit
commit 251ea6dfbdb4448875e41081682bb3aa451b5729
Author: Roger Sayle
Date: Fri Mar 11 17:57:12 2022 +
PR tree-optimization/98335: New peephole2 xorl;movb -> movzbl
caused
FAIL: libitm.c/memcpy-1.c
On 3/10/22 16:57, Patrick Palka wrote:
On Thu, 10 Mar 2022, Jason Merrill wrote:
On 2/16/22 15:56, Patrick Palka wrote:
On Tue, 15 Feb 2022, Jason Merrill wrote:
On 2/14/22 11:32, Patrick Palka wrote:
Here the template context for the atomic constraint has two levels of
template
On 3/11/22 11:46, Patrick Palka wrote:
On Thu, 10 Mar 2022, Jason Merrill wrote:
On 3/1/22 00:10, Patrick Palka wrote:
On Tue, 19 Jan 2021, Jason Merrill wrote:
On 1/13/21 12:05 PM, Patrick Palka wrote:
In the below testcase, the expression of the atomic constraint after
substitution is
On 2/17/22 23:30, Zhao Wei Liew wrote:
On Fri, 18 Feb 2022 at 08:32, Zhao Wei Liew wrote:
+/* Test non-empty class */
+void f2(B b1, B b2)
+{
+ if (b1 = 0); /* { dg-warning "suggest parentheses" } */
+ if (b1 = 0.); /* { dg-warning "suggest parentheses" } */
+ if (b1 = b2); /* { dg-warning
Fixes: 77eccbf39ed5
rs6000.h has
#define PROCESSOR_POWERPC PROCESSOR_PPC604
#define PROCESSOR_POWERPC64 PROCESSOR_RS64A
which means that if you use things like -mcpu=powerpc -mvsx it will no
longer work after my latest .machine patch. This causes GCC build errors
in some cases, not a
Hi, Ruoyao,
(I might not be able to reply to this thread till next Wed due to a short
vacation).
First, some comments on opening bugs against Gcc:
I took a look at the bug reports PR104817 and PR104820:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
On Fri, Mar 11, 2022 at 09:57:50PM +0100, Jakub Jelinek wrote:
> On Fri, Mar 11, 2022 at 02:51:23PM -0600, Segher Boessenkool wrote:
> > On Fri, Mar 11, 2022 at 08:42:27PM +, Joseph Myers wrote:
> > > The version of this patch applied to GCC 10 branch (commit
> > >
On Fri, Mar 11, 2022 at 02:51:23PM -0600, Segher Boessenkool wrote:
> On Fri, Mar 11, 2022 at 08:42:27PM +, Joseph Myers wrote:
> > The version of this patch applied to GCC 10 branch (commit
> > 641b407763ecfee5d4ac86d8ffe9eb1eeea5fd10) has broken the glibc build for
> >
On Fri, 11 Mar 2022, Krishna Narayanan via Gcc-patches wrote:
> Hello,
> The following is a patch for the PR92209,which gives a warning when
> the function prototype does not specify its argument type.In this
> patch there has been a change in the warning message displayed for
>
On Fri, Mar 11, 2022 at 08:42:27PM +, Joseph Myers wrote:
> The version of this patch applied to GCC 10 branch (commit
> 641b407763ecfee5d4ac86d8ffe9eb1eeea5fd10) has broken the glibc build for
> powerpc64le-linux-gnu (it's fine with GCC 11 branch and master, just GCC
> 10 branch is broken)
The version of this patch applied to GCC 10 branch (commit
641b407763ecfee5d4ac86d8ffe9eb1eeea5fd10) has broken the glibc build for
powerpc64le-linux-gnu (it's fine with GCC 11 branch and master, just GCC
10 branch is broken)
On Fri, Mar 11, 2022 at 01:07:29AM -0500, Michael Meissner wrote:
> Fix DImode to TImode sign extend issue, PR target/104898
> When I wrote the extendditi2 pattern, I forgot that mtvsrdd had that
> behavior so I used a 'r' constraint instead of 'b'. In the rare case
> where the value is in GPR
On Wed, Feb 16, 2022 at 5:28 AM H.J. Lu wrote:
>
> ---
> htdocs/gcc-12/changes.html | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html
> index b6341fda..7d253f29 100644
> --- a/htdocs/gcc-12/changes.html
> +++
On 3/11/22 18:59, Jonathan Wakely wrote:
Thanks. Now I'm getting a build failure because libtol wasn't created
in the avr/libstdc++-v3 directory of the build tree, but I'll have to
look into that next week.
/bin/sh: ../libtool: No such file or directory
Here's my configure call:
I'm going to push this as obvious, but do I need to do anything special
to sync it with binutils, or will that happen next time somebody needs a
proper fix?
-- >8 --
The custom option for enabling/disabling libstdc++ is not spelled the
same as the directory name:
AC_ARG_ENABLE(libstdcxx,
Patrick, I think this is right, but please take a look to double check.
I think we should fix the feature-test macro conditions for gcc-11 too,
although it's a bit more complicated there. It should depend on IEEE
float and double *and* uselocale. We don't need the other changes on the
branch.
On Fri, 11 Mar 2022 at 15:35, Detlef Vollmann wrote:
>
> On 3/11/22 16:12, Jonathan Wakely wrote:
> > On Fri, 11 Mar 2022 at 14:28, Detlef Vollmann wrote:
> >> With this and the other fix I was able to build the complete
> >> libstdc++ for AVR based on AVR Libc 2.0 (plus some ad hoc
> >> AVR
The "sorry, unimplemented" message in the new g++.dg/other/pr84964.C is
apparently dependent upon whether the target passes multi-gigabyte
arguments on the stack. This tweaks the testcase to just confirm that
it no longer ICEs, not the specific set of warnings/errors triggered.
Committed as
On Sat, 2022-03-12 at 01:29 +0800, Xi Ruoyao via Gcc-patches wrote:
> I'm now thinking: is there always at least one *GPR* which need to be
> cleared? If it's true, let's say GPR $12, and fcc0 & fcc2 needs to be
> cleared, we can use something like:
>
> cfc1 $12, $25
> andi $25, 5
$12, 5.
I
On Fri, 2022-03-11 at 16:08 +, Qing Zhao wrote:
> Why there is “mthi $0” instruction, but there is NO emit_move_insn(HI,
> CONST_0)?
> Is such mismatch a bug? If not, why?
>
> > In theory it's possible
> > to emit the mthi instruction explicitly here though, but we'll need to
> > clear
Matheus Castanho reports that the patch I posted fixes the problem in the
1040868 bug report.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meiss...@linux.ibm.com
Hi Jeff and David,
any news on this fix?
Thanks,
Marc
Am Mo., 31. Jan. 2022 um 12:42 Uhr schrieb Marc Nieper-Wißkirchen
:
>
> Attached to this email is the patch updated to the recent renaming from *.c
> to *.cc.
>
>
> Am So., 23. Jan. 2022 um 14:18 Uhr schrieb Marc Nieper-Wißkirchen
> :
>>
Hi,
I plan to backport the patch to fix PR100775:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100775
To gcc11 since this is a general bug to -fzero-call-used-regs. And should be
fixed in gcc11 as well.
I have tested the patch with gcc11 release branch on both x86 and aarch64, no
> On Mar 10, 2022, at 8:54 PM, Xi Ruoyao wrote:
>
> On Thu, 2022-03-10 at 20:31 +, Qing Zhao wrote:
>
+ SET_HARD_REG_BIT (zeroed_hardregs, HI_REGNUM);
+ if (TEST_HARD_REG_BIT (need_zeroed_hardregs, LO_REGNUM))
+ SET_HARD_REG_BIT (zeroed_hardregs, LO_REGNUM);
On Thu, 10 Mar 2022, Jason Merrill wrote:
> On 3/1/22 00:10, Patrick Palka wrote:
> > On Tue, 19 Jan 2021, Jason Merrill wrote:
> >
> > > On 1/13/21 12:05 PM, Patrick Palka wrote:
> > > > In the below testcase, the expression of the atomic constraint after
> > > > substitution is (int *)
On 3/11/22 16:12, Jonathan Wakely wrote:
On Fri, 11 Mar 2022 at 14:28, Detlef Vollmann wrote:
With this and the other fix I was able to build the complete
libstdc++ for AVR based on AVR Libc 2.0 (plus some ad hoc
AVR header fixes) from git master 5e28be89.
Nice. I finally figure out that I
On Fri, 11 Mar 2022 at 15:12, Jonathan Wakely wrote:
>
> On Fri, 11 Mar 2022 at 14:28, Detlef Vollmann wrote:
> >
> > Hi Jonathan,
> >
> > On 3/10/22 22:11, Jonathan Wakely wrote:
> >
> > > Tested x86_64-linux, pushed to trunk.
> >
> > Thanks.
> > With this and the other fix I was able to build
On Fri, 11 Mar 2022 at 14:28, Detlef Vollmann wrote:
>
> Hi Jonathan,
>
> On 3/10/22 22:11, Jonathan Wakely wrote:
>
> > Tested x86_64-linux, pushed to trunk.
>
> Thanks.
> With this and the other fix I was able to build the complete
> libstdc++ for AVR based on AVR Libc 2.0 (plus some ad hoc
>
Hi Jonathan,
On 3/10/22 22:11, Jonathan Wakely wrote:
Tested x86_64-linux, pushed to trunk.
Thanks.
With this and the other fix I was able to build the complete
libstdc++ for AVR based on AVR Libc 2.0 (plus some ad hoc
AVR header fixes) from git master 5e28be89.
And a small example with
Hi!
On Thu, Mar 10, 2022 at 09:54:55AM -0800, Patrick O'Neill wrote:
> I added this enforcement during the combine pass since it looks at the
> cost of certian expressions and can rely on the target to tell the
> pass that clobber-ops are cheaper than regular ops.
That is not a reason to put
Minor remark to the test:
On 11.03.22 13:30, Marcel Vollweiler wrote:
+ int d = omp_get_default_device ();
...
+ int shared_mem = 0;
+ #pragma omp target map (alloc: shared_mem) device (d)
+shared_mem = 1;
+ if (omp_target_is_accessible (p, sizeof (int), d) != shared_mem)
+
The following addresses optimistic non-addressable marking of
an argument of __atomic_compare_exchange_n which broke when
I added DECL_NOT_GIMPLE_REG_P since we cannot guarantee we can
rewrite it when TREE_ADDRESSABLE is unset. Instead we have to
restore TREE_ADDRESSABLE in that case.
On Fri, Mar 11, 2022 at 8:43 PM Richard Biener via Gcc-patches
wrote:
>
> After accounting for GPR -> XMM move cost for vec_construct the
> base cost needs adjustments to not double-cost those. This also
> lowers the cost when such move is not necessary.
>
> This fixes the observed 538.imagick_r
After accounting for GPR -> XMM move cost for vec_construct the
base cost needs adjustments to not double-cost those. This also
lowers the cost when such move is not necessary.
This fixes the observed 538.imagick_r and 525.x264_r regressions
for me on Zen2 with -Ofast -march=native.
Hi,
This patch adds the OpenMP runtime routine "omp_target_is_accessible" which was
introduced in OpenMP 5.1 (specification section 3.8.4):
"The omp_target_is_accessible routine tests whether host memory is accessible
from a given device."
"This routine returns true if the storage of size
On Fri, Mar 11, 2022 at 12:44 PM Tobias Burnus wrote:
>
> This patch removes the last(?) -save-temps file that is still written to /tmp.
>
> Thus, instead of
>
> .../12.0.1/lto-wrapper -fresolution=a.res -flinker-output=exec
> -foffload-objects=/tmp/ccyXiCap.ofldlist
> .../12.0.1/lto-wrapper
This patch removes the last(?) -save-temps file that is still written to /tmp.
Thus, instead of
.../12.0.1/lto-wrapper -fresolution=a.res -flinker-output=exec
-foffload-objects=/tmp/ccyXiCap.ofldlist
.../12.0.1/lto-wrapper -fresolution=a.res -flinker-output=exec
On Wed, Mar 9, 2022 at 6:43 PM Roger Sayle wrote:
>
>
> Hi Richard,
> Many thanks. Yes, your proposed ao_ref_alignment is exactly what I was
> looking for.
> Here's the second revision of my patch for PR tree-optimization/98335 that
> both uses/
> introduces ao_ref_alignment and more
On Fri, Mar 11, 2022 at 12:31 AM Roger Sayle wrote:
>
>
> This patch addresses PR middle-end/98420, which is inappropriate constant
> folding of x - x to 0.0 (in match.pd) when -frounding-math is specified.
> Specifically, x - x may be -0.0 with FE_DOWNWARD as the rounding mode.
>
> To summarize,
On Thu, Mar 10, 2022 at 12:32 PM Xi Ruoyao wrote:
>
> On Thu, 2022-03-10 at 09:01 +0100, Richard Biener wrote:
> > On Wed, Mar 9, 2022 at 5:12 PM Xi Ruoyao
> > wrote:
> > >
> > > On Wed, 2022-03-09 at 15:55 +0100, Richard Biener wrote:
> > >
> > > > isn't it better to make targetm.const_anchor
Hello,
The following is a patch for the PR92209,which gives a warning when
the function prototype does not specify its argument type.In this
patch there has been a change in the warning message displayed for
-Wstrict-prototypes to specify its argument types.I have also added
the testcase for it.
Hi Patrick:
There is few direction in my mind:
1. Model the C extension right in riscv.md
2. Write peephole2 pattern.
3. Implement a RISC-V specific register renaming pass.
1. Model the C extension right in riscv.md
Currently we rely the GNU as to compress the instruction to C
extension, and
59 matches
Mail list logo
