The make silent the following 2 warnings:
jit/jit-playback.h:785:16: warning: private field 'm_source_file' is not used
[-Wunused-private-field]
jit/jit-playback.h:804:16: warning: private field 'm_line' is not used
[-Wunused-private-field]
gcc/jit/ChangeLog:
* jit-playback.h: Use unus
The patch fixes the following Clang warnings:
gcc/go/gofrontend/escape.cc:1290:17: warning: private field 'fn_' is not used
[-Wunused-private-field]
gcc/go/gofrontend/escape.cc:3478:19: warning: private field 'context_' is not
used [-Wunused-private-field]
gcc/go/gofrontend/lex.h:564:15: warning
Hi!
Lto profiledbootstrap was failing for me on {powerpc64le,s390x}-linux with
modula 2 enabled, with:
cc1gm2: internal compiler error: the location value is corrupt
0x11a3d2d m2assert_AssertLocation(unsigned int)
../../gcc/m2/gm2-gcc/m2assert.cc:40
0x11a3d2d m2statement_BuildAssignmentTre
Hi!
DECL_OMP_PRIVATIZED_MEMBER vars are artificial vars with DECL_VALUE_EXPR
of this->field used just during gimplification and omp lowering/expansion
to privatize individual fields in methods when needed.
As the following testcase shows, when not in templates, they were handled
right, but in temp
Hi,
This a different attempt from Mike's approach[1][2] to fix the
issue in PR107299. With option -mabi=ieeelongdouble specified,
type long double (and __float128) and _Float128 have the same
mode TFmode, but they have different type precisions, it causes
the assertion to fail in function fold_us
Jakub Jelinek writes:
> Hi!
>
> The r13-2943-g11a113d501ff64 made aarch64.h include
> aarch64-option-extensions.def, but that file isn't installed
> for building plugins.
>
> The following patch should fix that, ok for trunk if it
> passes bootstrap/regtest + building plugin against it?
>
> 2022-1
Am Dienstag, dem 20.12.2022 um 20:04 + schrieb Joseph Myers:
> On Tue, 20 Dec 2022, Martin Uecker via Gcc-patches wrote:
>
> > Here is a patch to remove the unused function
> > same_translation_unit_p and related code. The
> > code to check for structural equivalency of
> > structs / unions is
On Wed, Dec 21, 2022 at 09:56:33AM +, Richard Sandiford wrote:
> Jakub Jelinek writes:
> > The r13-2943-g11a113d501ff64 made aarch64.h include
> > aarch64-option-extensions.def, but that file isn't installed
> > for building plugins.
> >
> > The following patch should fix that, ok for trunk if
Tamar Christina writes:
> Hi All,
>
> The move, load, load, store, dup, basically all the non arithmetic FP16
> instructions use baseline armv8-a HF support, and so do not require the
> Armv8.2-a extensions. This relaxes the instructions.
>
> Bootstrapped Regtested on aarch64-none-linux-gnu and n
Jakub Jelinek writes:
> On Wed, Dec 21, 2022 at 09:56:33AM +, Richard Sandiford wrote:
>> Jakub Jelinek writes:
>> > The r13-2943-g11a113d501ff64 made aarch64.h include
>> > aarch64-option-extensions.def, but that file isn't installed
>> > for building plugins.
>> >
>> > The following patch s
> -Original Message-
> From: Richard Sandiford
> Sent: Wednesday, December 21, 2022 10:31 AM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; Marcus Shawcroft
> ; Kyrylo Tkachov
> Subject: Re: [PATCH]AArch64 relax constraints on FP16 insn PR108172
>
> Tamar
Tamar Christina writes:
>> -Original Message-
>> From: Richard Sandiford
>> Sent: Wednesday, December 21, 2022 10:31 AM
>> To: Tamar Christina
>> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
>> ; Marcus Shawcroft
>> ; Kyrylo Tkachov
>> Subject: Re: [PATCH]AArch64 relax constraints
Hi,
this patches updates documentation of -fwhole-program which was wrongly
claiming that it is useless with LTO whole it is useful for LTO without plugin
and extends -fwhole-program to also work with incremental linking when
non-LTO code is produced.
This is useful when building kernel where the i
The following avoids passing down error_mark_node to fold_convert.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR middle-end/107994
* gimplify.cc (gimplify_expr): Catch errorneous comparison
operand.
---
gcc/gimplify.cc | 6 --
1 file changed, 4 inser
Hello,
PR-108119 Disable m2 plugin m2rte (provide --enable-m2plugin configure option).
The m2 plugin m2rte attempts to find reachable calls to the m2 exception
handler, but it identifies the m2 exception calls by procedure name.
As this won't work with other languages it should be disabled by d
Jakub Jelinek writes:
> Hi!
>
> Lto profiledbootstrap was failing for me on {powerpc64le,s390x}-linux with
> modula 2 enabled, with:
> cc1gm2: internal compiler error: the location value is corrupt
> 0x11a3d2d m2assert_AssertLocation(unsigned int)
> ../../gcc/m2/gm2-gcc/m2assert.cc:40
> 0
On Wed, Dec 21, 2022 at 1:35 PM Gaius Mulley via Gcc-patches
wrote:
>
>
> Hello,
>
> PR-108119 Disable m2 plugin m2rte (provide --enable-m2plugin configure
> option).
>
> The m2 plugin m2rte attempts to find reachable calls to the m2 exception
> handler, but it identifies the m2 exception calls b
The addition of rust has pulled in libffi as a target library for Darwin.
This fails to bootstrap on some versions of i686-darwin and has build-time
diagnostics on all. The EH is also invalid and those tests fail.
Note that X86 Darwin is not listed as supported upstream.
However I have made a pul
Architectures like Mips are very limited when it comes to addressing modes.
Therefore, the expected
behavior would be that, for the BASE + OFFSET addressing mode, complexity is
lower, while, for more
complex addressing modes (e.g. BASE + INDEX << SCALE), which are not supported,
complexity is
hi
After f9f69dd, complexity is calculated using the
valid_mem_ref_p target hook. Architectures like Mips only
allow BASE + OFFSET addressing modes, which in turn prevents
the calculation of complexity for other addressing modes,
resulting in non-optimal candidate selection.
There still is code that
When there are enough registers, the register pressure cost is
unnecessarily bumped by adding another n_cands.
This behavior may result in register pressure costs for the case
when there are enough registers being higher than for other cases.
When there are enough registers, the register pressure
Hi, Richard,
Thanks a lot for your comments.
> On Dec 21, 2022, at 2:12 AM, Richard Biener wrote:
>
> On Tue, 20 Dec 2022, Qing Zhao wrote:
>
>> Hi,
>>
>> This is the patch for mentioning -fstrict-flex-arrays and -Warray-bounds=2
>> changes in gcc-13/changes.html.
>>
>> Let me know if you h
Here during ahead of time checking of C{}, we indirectly call get_nsdmi
for C::m from finish_compound_literal, which in turn calls
break_out_target_exprs for C::m's (non-templated) initializer, during
which we end up building a call to A::~A and checking expr_noexcept_p
for it (from build_vec_delet
On Wed, 21 Dec 2022, Patrick Palka wrote:
> Here during ahead of time checking of C{}, we indirectly call get_nsdmi
> for C::m from finish_compound_literal, which in turn calls
> break_out_target_exprs for C::m's (non-templated) initializer, during
> which we end up building a call to A::~A and ch
On 12/20/22 20:45, Andrew Pinski wrote:
On Tue, Dec 20, 2022 at 10:59 AM Tom Tromey wrote:
"Andrew" == apinski--- via Gdb-patches writes:
Andrew> From: Andrew Pinski
Andrew> This patch uses the toplevel configure parts for GMP/MPFR for
Andrew> gdb. The only thing is that gdb now requir
>> I think it's fine to move forward with this now.
>> Thank you again for doing this.
Andrew> Just to double check this is an approval?
Yes, sorry for being unclear.
Tom
Richard Biener writes:
>>
>> ChangeLog:
>>
>> * Makefile.def (extra_configure_flags): Add @enable_m2plugin@.
>> * Makefile.in : Rebuilt.
>> * configure : Rebuilt.
>> * configure.ac (host_tools): Remove unused gm2tools.
>> (m2plugin) New AC_ARG_ENABLE.
>>
Hi Gaius,
Btw., you've got a couple of formatting errors in your ChangeLog entires:
>>> ChangeLog:
>>>
>>> * Makefile.def (extra_configure_flags): Add @enable_m2plugin@.
>>> * Makefile.in : Rebuilt.
^ no blank here. Besides, the entires are
Related pending (simple) patches - aka *Patch Ping*:
* [Patch] Fortran: Extend align-clause checks of OpenMP's allocate clause
https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608401.html
* [Patch] OpenMP: Parse align clause in allocate directive in C/C++
https://gcc.gnu.org/pipermail
https://gcc.gnu.org/pipermail/gcc-patches/2022-August/599882.html
Submission Date- Wed, 17 Aug 2022
Upstream-Status: Submitted
The given GCC patch is with it’s current status as ‘Submitted’ but still is not
taken to the upstream. Please let us know about why the patch is not taken to
the upstrea
From: Christoph Müllner
This series adds basic support for the vector crypto extensions:
* Zvkb
* Zvkg
* Zvkh[a,b]
* Zvkn
* Zvksed
* Zvksh
The implementation follows the version 20221220 of the specification,
which can be found here:
https://github.com/riscv/riscv-crypto/releases/tag/v20221220
Rainer Orth writes:
> Hi Gaius,
>
> Btw., you've got a couple of formatting errors in your ChangeLog entires:
>
ChangeLog:
* Makefile.def (extra_configure_flags): Add @enable_m2plugin@.
* Makefile.in : Rebuilt.
> ^ no blank here. Besid
On Mon, Dec 19, 2022 at 8:52 PM Hongtao Liu wrote:
>
> On Thu, Dec 15, 2022 at 3:45 PM Hongtao Liu wrote:
> >
> > On Thu, Dec 15, 2022 at 3:39 PM Jakub Jelinek wrote:
> > >
> > > On Thu, Dec 15, 2022 at 02:21:37PM +0800, liuhongt via Gcc-patches wrote:
> > > > --- a/gcc/config/i386/i386.opt
> >
Hi!
On Wed, Dec 21, 2022 at 05:02:17PM +0800, Kewen.Lin wrote:
> This a different attempt from Mike's approach[1][2] to fix the
> issue in PR107299.
Ke Wen, Mike: so iiuc with this patch applied all three of Mike's
patches are unnecessary?
> With option -mabi=ieeelongdouble specified,
> type lon
On Wed, 21 Dec 2022, Segher Boessenkool wrote:
> > --- a/gcc/tree.cc
> > +++ b/gcc/tree.cc
> > @@ -9442,15 +9442,6 @@ build_common_tree_nodes (bool signed_char)
> >if (!targetm.floatn_mode (n, extended).exists (&mode))
> > continue;
> >int precision = GET_MODE_PRECISION (mode);
On 12/21/22 09:52, Patrick Palka wrote:
Here during ahead of time checking of C{}, we indirectly call get_nsdmi
for C::m from finish_compound_literal, which in turn calls
break_out_target_exprs for C::m's (non-templated) initializer, during
which we end up building a call to A::~A and checking ex
Hi,
The first patch in the series is just a minor test cleanup that I did to
make sure all tests in a test case run (instead of aborting at first
failure) and print the ones that failed. The second patch is the actual
fix.
The patch intends to make __bos/__bdos do the right thing with structs
co
The tree object size pass tries to fail when it detects a flex array in
the struct, but it ends up doing the right thing only when the flex
array is in the outermost struct. For nested cases (such as arrays
nested in a union or an inner struct), it ends up taking whatever value
the flex array is d
Instead of failing on first error, run all __builtin_object_size and
__builtin_dynamic_object_size tests to completion and then provide a
summary of which tests failed.
gcc/testsuite/ChangeLog:
* gcc.dg/builtin-dynamic-object-size-0.c: Move FAIL and nfail
into...
* gcc.dg/
On Wed, Dec 21, 2022 at 12:20:23PM -0800, H.J. Lu wrote:
> On Mon, Dec 19, 2022 at 8:52 PM Hongtao Liu wrote:
> >
> > On Thu, Dec 15, 2022 at 3:45 PM Hongtao Liu wrote:
> > >
> > > On Thu, Dec 15, 2022 at 3:39 PM Jakub Jelinek wrote:
> > > >
> > > > On Thu, Dec 15, 2022 at 02:21:37PM +0800, liuh
On Wed, Dec 21, 2022 at 2:35 PM Jakub Jelinek wrote:
>
> On Wed, Dec 21, 2022 at 12:20:23PM -0800, H.J. Lu wrote:
> > On Mon, Dec 19, 2022 at 8:52 PM Hongtao Liu wrote:
> > >
> > > On Thu, Dec 15, 2022 at 3:45 PM Hongtao Liu wrote:
> > > >
> > > > On Thu, Dec 15, 2022 at 3:39 PM Jakub Jelinek w
On Wed, Dec 21, 2022 at 09:40:24PM +, Joseph Myers wrote:
> On Wed, 21 Dec 2022, Segher Boessenkool wrote:
>
> > > --- a/gcc/tree.cc
> > > +++ b/gcc/tree.cc
> > > @@ -9442,15 +9442,6 @@ build_common_tree_nodes (bool signed_char)
> > >if (!targetm.floatn_mode (n, extended).exists (&mode
On Wed, Dec 21, 2022 at 02:43:43PM -0800, H.J. Lu wrote:
> > > > > > > Target RejectNegative
> > > > > > > Set 80387 floating-point precision to 80-bit.
> > > > > > >
> > > > > > > +mdaz-ftz
> > > > > > > +Target
> > > > > >
> > > > > > s/Target/Driver/
> > > > > Change to Driver and Got error li
On Thu, Dec 22, 2022 at 6:46 AM Jakub Jelinek wrote:
>
> On Wed, Dec 21, 2022 at 02:43:43PM -0800, H.J. Lu wrote:
> > > > > > > > Target RejectNegative
> > > > > > > > Set 80387 floating-point precision to 80-bit.
> > > > > > > >
> > > > > > > > +mdaz-ftz
> > > > > > > > +Target
> > > > > > >
>
Hi Segher,
on 2022/12/22 05:24, Segher Boessenkool wrote:
> Hi!
>
> On Wed, Dec 21, 2022 at 05:02:17PM +0800, Kewen.Lin wrote:
>> This a different attempt from Mike's approach[1][2] to fix the
>> issue in PR107299.
>
> Ke Wen, Mike: so iiuc with this patch applied all three of Mike's
> patches a
Hi Joseph,
on 2022/12/22 05:40, Joseph Myers wrote:
> On Wed, 21 Dec 2022, Segher Boessenkool wrote:
>
>>> --- a/gcc/tree.cc
>>> +++ b/gcc/tree.cc
>>> @@ -9442,15 +9442,6 @@ build_common_tree_nodes (bool signed_char)
>>>if (!targetm.floatn_mode (n, extended).exists (&mode))
>>> contin
On Wed, 21 Dec 2022, Qing Zhao wrote:
> Hi, Richard,
>
> Thanks a lot for your comments.
>
> > On Dec 21, 2022, at 2:12 AM, Richard Biener wrote:
> >
> > On Tue, 20 Dec 2022, Qing Zhao wrote:
> >
> >> Hi,
> >>
> >> This is the patch for mentioning -fstrict-flex-arrays and -Warray-bounds=2
>
Hi,
On 2022-12-21 15:30, Richard Biener wrote:
On Wed, 21 Dec 2022, Jiufu Guo wrote:
Hi,
This patch is fixing an issue about parameter accessing if the
parameter is struct type and passed through integer registers, and
there is floating member is accessed. Like below code:
typedef struct DF
On Thu, 22 Dec 2022, guojiufu wrote:
> Hi,
>
> On 2022-12-21 15:30, Richard Biener wrote:
> > On Wed, 21 Dec 2022, Jiufu Guo wrote:
> >
> >> Hi,
> >>
> >> This patch is fixing an issue about parameter accessing if the
> >> parameter is struct type and passed through integer registers, and
> >>
49 matches
Mail list logo
