https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108199
--- Comment #7 from Andreas Krebbel ---
(In reply to Andrew Pinski from comment #6)
> (In reply to Andreas Krebbel from comment #5)
> > In:
> >
> > _1 = src_6(D)->a;
> > dst$val_9 = _1;
> > _2 = BIT_FIELD_REF ;
> > _3 = _2 & 64;
> >
On Fri, Dec 23, 2022 at 12:19 AM Roger Sayle wrote:
>
>
> This patch enhances x86's STV pass to handle VEC_SELECT during general
> scalar chain conversion, performing SImode scalar extraction from V4SI
> and DImode scalar extraction from V2DI vector registers.
>
> The motivating test case from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108117
--- Comment #16 from Alexander Monakov ---
Draft patch for the sched1 issue:
https://inbox.sourceware.org/gcc-patches/cf62c3ec-0a9e-275e-5efa-2689ff1f0...@ispras.ru/T/#m95238afa0f92daa0ba7f8651741089e7cfc03481
On Thu, 22 Dec 2022, Qing Zhao wrote:
> > I think scheduling across calls in the pre-RA scheduler is simply an
> > oversight,
> > we do not look at dataflow information and with 50% chance risk extending
> > lifetime of a pseudoregister across a call, causing higher register
> > pressure at
>
On Fri, Dec 23, 2022 at 12:09 AM Roger Sayle wrote:
>
>
> With many thanks to H.J. for doing all the hard work, this patch resolves
> two P1 regressions; PR target/106933 and PR target/106959.
>
> Although superficially similar, the i386 backend's two scalar-to-vector
> (STV) passes perform their
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108206
--- Comment #1 from Arseny Solokha ---
> % g++-13 -c vph5xonf.cc
> vph5xonf.cc:1:11: error: 'WrongType' has not been declared
> 1 | template void foo (T1);
> | ^
> vph5xonf.cc:2:11: error: 'WrongType' has not been
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108206
Bug ID: 108206
Summary: ICE: tree check: expected tree that contains 'decl
minimal' structure, have 'error_mark' in
merge_default_template_args, at cp/decl.cc:1563
From 21904908689318ab81c630adc8cc7067e1a12488 Mon Sep 17 00:00:00 2001
From: Jin Ma
Date: Fri, 23 Dec 2022 10:42:19 +0800
Subject: [PATCH 1/1] Fixed typo
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc:
---
gcc/common/config/riscv/riscv-common.cc | 2 +-
1 file changed, 1
Committed, thanks :)
Ju-Zhe has not figured out how to commit to his environment yet, I am
helping him to set up.
On Wed, Dec 21, 2022 at 7:38 AM Palmer Dabbelt wrote:
>
> On Tue, 20 Dec 2022 15:33:11 PST (-0800), juzhe.zh...@rivai.ai wrote:
> > Thanks. I received an email from sourceware:
> >
Committed, thanks :)
On Tue, Dec 20, 2022 at 11:57 PM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 12/20/22 07:58, juzhe.zh...@rivai.ai wrote:
> > From: Ju-Zhe Zhong
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv-vector-builtins-shapes.cc (struct
> > vsetvl_def): Add "__riscv_"
Committed, thanks :)
On Wed, Dec 21, 2022 at 12:00 AM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 12/20/22 07:51, juzhe.zh...@rivai.ai wrote:
> > From: Ju-Zhe Zhong
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv-vector-builtins-bases.cc: Remove side effects.
> OK.
> Jeff
Committed, thanks :)
On Fri, Dec 23, 2022 at 8:57 AM 钟居哲 wrote:
>
> This patch is minimum intrinsics support for VSETVL PASS to support AVL model.
> The corresponding unit-test for vle.v/vse.v should be added after I support
> AVL model
> and well tested VSETVL PASS patch.
>
>
>
Committed, thanks :)
On Tue, Dec 20, 2022 at 11:59 PM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 12/20/22 07:56, juzhe.zh...@rivai.ai wrote:
> > From: Ju-Zhe Zhong
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv-vector-builtins-bases.cc: Change it to no
> > side effects.
> >
Committed, thanks :)
On Tue, Dec 20, 2022 at 8:28 AM Jeff Law via Gcc-patches
wrote:
>
>
>
> On 12/19/22 16:09, juzhe.zh...@rivai.ai wrote:
> > From: Ju-Zhe Zhong
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv-vsetvl.cc (vlmax_avl_insn_p): Fix multi-line
> > conditional.
> >
Committed, thanks :)
On Fri, Dec 23, 2022 at 11:33 AM wrote:
>
> From: Ju-Zhe Zhong
>
> gcc/ChangeLog:
>
> * config/riscv/vector.md: Fix contraints.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/base/vle-constraint-1.c: New test.
>
> ---
> gcc/config/riscv/vector.md
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106731
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:7e76cd96950f49ce21246d44780e972d86b2bcdd
commit r13-4862-g7e76cd96950f49ce21246d44780e972d86b2bcdd
Author: Steve Kargl
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108205
Bug ID: 108205
Summary: ICE following "unused parameter" in precondition
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106731
--- Comment #9 from Jerry DeLisle ---
(In reply to Jerry DeLisle from comment #8)
> The simple patch does indeed fix the ICE at compile time. It also
> regression tests cleanly.
>
> I am studying the results of running this test case to be
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/vector.md: Fix contraints.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/base/vle-constraint-1.c: New test.
---
gcc/config/riscv/vector.md| 16 +--
.../riscv/rvv/base/vle-constraint-1.c | 109
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106731
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
---
> From: Jonathan Wakely via Gcc-patches
> Date: Fri, 23 Dec 2022 00:37:04 +0100
> This is the largest missing piece of C++20 support. Only the cxx11 ABI
> is supported, due to the use of std::string in the API for time zones.
> libstdc++-v3/ChangeLog:
>
> * acinclude.m4
This patch is minimum intrinsics support for VSETVL PASS to support AVL model.
The corresponding unit-test for vle.v/vse.v should be added after I support AVL
model
and well tested VSETVL PASS patch.
juzhe.zh...@rivai.ai
From: juzhe.zhong
Date: 2022-12-23 08:52
To: gcc-patches
CC:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107778
--- Comment #10 from W E Brown ---
> On Dec 22, 2022, at 6:51 PM, cvs-commit at gcc dot gnu.org
> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107778
>
> --- Comment #9 from CVS Commits ---
> The master branch has been updated
From: Ju-Zhe Zhong
gcc/ChangeLog:
* config/riscv/riscv-protos.h (get_avl_type_rtx): New function.
* config/riscv/riscv-v.cc (get_avl_type_rtx): Ditto.
* config/riscv/riscv-vector-builtins-bases.cc (class loadstore): New
class.
(BASE): Ditto.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107792
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:8ec5fcb6fc79e5bcca23c3fecbaf09d4566cb1d5
commit r13-4861-g8ec5fcb6fc79e5bcca23c3fecbaf09d4566cb1d5
Author: Arsen ArsenoviÄ
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107778
--- Comment #9 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:8ec5fcb6fc79e5bcca23c3fecbaf09d4566cb1d5
commit r13-4861-g8ec5fcb6fc79e5bcca23c3fecbaf09d4566cb1d5
Author: Arsen ArsenoviÄ
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108204
--- Comment #2 from nightstrike ---
(In reply to Andrew Pinski from comment #1)
> Try with -fno-ms-extensions or try -fms-extension on Linux.
Hey, we have a winner! -fms-extension on Linux results in the bad error, and
-fno-ms-extensions on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108204
--- Comment #1 from Andrew Pinski ---
Try with -fno-ms-extensions or try -fms-extension on Linux.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108204
Bug ID: 108204
Summary: pr84973-2.C fails with wrong error on mingw
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88322
Bug 88322 depends on bug 104166, which changed state.
Bug 104166 Summary: Implement C++20 std::format
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104166
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104166
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104167
--- Comment #3 from Jonathan Wakely ---
Time zones committed as r13-4853-g9fc61d45fa15fd
Formatting committed as r13-4856-gf99b94865fa629
Still missing std::chrono::parse.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108200
--- Comment #3 from Jonathan Wakely ---
And I've just added a few more at r13-4856-gf99b94865fa629
FAIL: 20_util/duration/io.cc (test for excess errors)
UNRESOLVED: 20_util/duration/io.cc compilation failed to produce executable
FAIL:
Tested x86_64-linux. Pushed to trunk. Backport to gcc-12 needed too.
-- >8 --
The commit r12-5877-g9e18a25331fa25 removed the incorrect
noexcept-specifier from std::condition_variable::wait and gave the new
symbol version @@GLIBCXX_3.4.30. It also redefined the original symbol
Another big missing piece of C++20 support, but header-only this time so
no new symbol exports. The last thing missing for C++20 is
std::chrono::parse.
Tested x86_64-linux, sparc-solaris2.11, powerpc-aix. Pushed to trunk.
-- >8 --
This adds the operator<< overloads and std::formatter
Tested x86_64-linux, sparc-solaris2.11, powerpc-aix. Pushed to trunk.
-- >8 --
Add a new __format::__write_padded_as_spec helper to remove duplicated
code in formatter specializations.
libstdc++-v3/ChangeLog:
* include/std/format (__format::__write_padded_as_spec): New
mingw stdio.h plays horrible games with extern "C++", but it also seems
sloppy for coro.h to declare printf in testcases that will also include
standard headers.
gcc/testsuite/ChangeLog:
* g++.dg/coroutines/coro.h: #include instead of
declaring puts/printf.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108203
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
This is the finished version of the last patch I posted before the end
of stage 1. This is quite late for stage 1 (!) and adds new symbols to
the shared library, but I'm pushing it now as it's an important piece of
C++20 support. As noted in the commit message, the symbols being added
are stable
These should really have tests for the new types, but I've been using
them heavily for a few weeks and they work well. I would rather get them
committed now and add tests later.
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* python/libstdcxx/v6/printers.py
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105730
--- Comment #11 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:ee4af2ed0b7322884ec4ff537564683c3749b813
commit r13-4857-gee4af2ed0b7322884ec4ff537564683c3749b813
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108203
Bug ID: 108203
Summary: Format string checking with __USE_MINGW_ANSI_STDIO
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
This patch enhances x86's STV pass to handle VEC_SELECT during general
scalar chain conversion, performing SImode scalar extraction from V4SI
and DImode scalar extraction from V2DI vector registers.
The motivating test case from bugzilla is:
typedef unsigned int v4si
With many thanks to H.J. for doing all the hard work, this patch resolves
two P1 regressions; PR target/106933 and PR target/106959.
Although superficially similar, the i386 backend's two scalar-to-vector
(STV) passes perform their transformations in importantly different ways.
The original pass
Jason Merrill writes:
> Aha, I wonder why the original tests have the terminal *? Testcases elsewhere
> in the testsuite that check for (\n|\r\n|\r) don't use *. I think I'll drop
> the * from both the tests and the script.
>
> Jason
Yep, that sounds reasonable. I'm not sure why, the
On Thu, 22 Dec 2022, Jason Merrill wrote:
> On 12/22/22 16:41, Patrick Palka wrote:
> > On Thu, 22 Dec 2022, Jason Merrill wrote:
> >
> > > On 12/22/22 11:31, Patrick Palka wrote:
> > > > On Wed, 21 Dec 2022, Jason Merrill wrote:
> > > >
> > > > > On 12/21/22 09:52, Patrick Palka wrote:
> > > >
Snapshot gcc-10-20221222 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20221222/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Wed, Dec 21, 2022 at 12:05 AM Martin Liška wrote:
>
> 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
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108200
Jonathan Wakely changed:
What|Removed |Added
Summary|std::format fails on AIX|std::format fails on AIX
On 12/22/22 16:56, Arsen Arsenović wrote:
Hi,
Jason Merrill writes:
+# Newlines should be more tolerant.
+s/\n$/(\\n|\\r\\n|\\r)*/;
Isn't specifically handling \\r\\n redundant with the * operator?
To the extent of my knowledge, yes; I left that in since the original
tests I was
LGTM
On Thu, Dec 22, 2022, 22:44 Jakub Jelinek wrote:
> On Thu, Dec 22, 2022 at 08:46:33PM +0100, Aldy Hernandez wrote:
> > I haven't looked at your problem above, but have you tried using
> > int_range_max (or even int_range<2>) instead of value_range above?
> >
> > value_range is deprecated
On Thu, Dec 22, 2022 at 07:48:28PM +, Joseph Myers wrote:
> On Thu, 22 Dec 2022, Segher Boessenkool wrote:
> > On Wed, Dec 21, 2022 at 09:40:24PM +, Joseph Myers wrote:
> > > On Wed, 21 Dec 2022, Segher Boessenkool wrote:
> > > > Joseph: what do you think about this patch? Is the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69604
--- Comment #16 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:794af0d00b7086c9f0493f3a1aaac644e1fd50f6
commit r13-4851-g794af0d00b7086c9f0493f3a1aaac644e1fd50f6
Author: Harald Anlauf
Date:
On 12/22/22 16:41, Patrick Palka wrote:
On Thu, 22 Dec 2022, Jason Merrill wrote:
On 12/22/22 11:31, Patrick Palka wrote:
On Wed, 21 Dec 2022, Jason Merrill wrote:
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
Hi,
Jason Merrill writes:
>> +# Newlines should be more tolerant.
>> +s/\n$/(\\n|\\r\\n|\\r)*/;
>
> Isn't specifically handling \\r\\n redundant with the * operator?
To the extent of my knowledge, yes; I left that in since the original
tests I was replacing with this script also used
On Thu, 22 Dec 2022 at 21:41, Jason Merrill via Libstdc++
wrote:
>
> On 12/22/22 06:03, Arsen Arsenović wrote:
> > From: Jonathan Wakely
> >
> > Make the output more readable. Don't output anything unless verbose
> > termination is enabled at configure-time.
>
> LGTM if Jonathan agrees. The
On Thu, Dec 22, 2022 at 10:13:04PM +0100, Harald Anlauf via Fortran wrote:
>
> the attached patch adds a check for statement function bodies for
> invalid uses of dummy arguments. This fixes an ICE-on invalid.
>
> Regtested on x86_64-pc-linux-gnu. OK for mainline?
>
Yes. Thanks for the
On 12/22/22 05:32, Jakub Jelinek wrote:
Hi!
On the following testcase, we warn with -Wunused-value twice, once
in the FEs and later on cgraphunit again with slightly different
wording.
The following patch fixes that by registering a warning suppression in the
FEs when we warn and not warning
On Thu, Dec 22, 2022 at 08:46:33PM +0100, Aldy Hernandez wrote:
> I haven't looked at your problem above, but have you tried using
> int_range_max (or even int_range<2>) instead of value_range above?
>
> value_range is deprecated and uses the legacy anti-range business,
> which has a really hard
On 12/22/22 06:03, Arsen Arsenović wrote:
This script is a helper used to generate dg-output lines from an existing
program output conveniently. It takes care of escaping Tcl and ARE stuff.
contrib/ChangeLog:
* dg-out-generator.pl: New file.
---
I updated this file to include the
On Thu, 22 Dec 2022, Jason Merrill wrote:
> On 12/22/22 11:31, Patrick Palka wrote:
> > On Wed, 21 Dec 2022, Jason Merrill wrote:
> >
> > > 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
On 12/22/22 06:03, Arsen Arsenović wrote:
From: Jonathan Wakely
Make the output more readable. Don't output anything unless verbose
termination is enabled at configure-time.
LGTM if Jonathan agrees. The testsuite changes should be applied in the
same commit.
libstdc++-v3/ChangeLog:
On 12/22/22 11:31, Patrick Palka wrote:
On Wed, 21 Dec 2022, Jason Merrill wrote:
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108200
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
> On 22 Dec 2022, at 21:15, Jason Merrill wrote:
>
> On 12/4/22 11:30, Iain Sandoe wrote:
>> This fixes a long-standing problem on Darwin where we cannot independently
>> set
>> -static-libstdc++ because the flag gets stripped by the g++ driver.
>> This patch is essentially the same as the
On 12/4/22 11:30, Iain Sandoe wrote:
This fixes a long-standing problem on Darwin where we cannot independently set
-static-libstdc++ because the flag gets stripped by the g++ driver.
This patch is essentially the same as the one used for the 'D' driver and has
been in local use for some time.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69604
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||accepts-invalid,
Dear all,
the attached patch adds a check for statement function bodies for
invalid uses of dummy arguments. This fixes an ICE-on invalid.
Regtested on x86_64-pc-linux-gnu. OK for mainline?
Thanks,
Harald
From 794af0d00b7086c9f0493f3a1aaac644e1fd50f6 Mon Sep 17 00:00:00 2001
From: Harald
On 12/22/22 12:34, Patrick Palka wrote:
On Thu, 15 Dec 2022, Jason Merrill wrote:
On 12/15/22 14:31, Patrick Palka wrote:
On Thu, 15 Dec 2022, Patrick Palka wrote:
On Thu, 15 Dec 2022, Jason Merrill wrote:
On 12/12/22 12:20, Patrick Palka wrote:
When instantiating a constrained hidden
This adds regression tests for an ICE on valid code that
seems gone on trunk, but the cause is still unclear.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103770
regressions tests for PR103770
This adds tests from bugzilla for PR103770 and duplicates.
testsuite/gcc.dg/
*
On Thu, 22 Dec 2022, Segher Boessenkool wrote:
> Hi!
>
> 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)
On Thu, Dec 22, 2022 at 1:54 PM Jakub Jelinek wrote:
>
> On Thu, Dec 22, 2022 at 01:09:21PM +0100, Aldy Hernandez wrote:
> > INTEGER_CST singleton and
> > > union that into the SSA_NAMEs range and then do set_range_info
> > > with the altered range I guess.
> > >
> >
> > Note that set_range_info
> On Dec 22, 2022, at 12:56 PM, Alexander Monakov wrote:
>
>
> On Thu, 22 Dec 2022, Jose E. Marchesi via Gcc-patches wrote:
>
>> The first instruction scheduler pass reorders instructions in the TRY
>> block in a way `b=true' gets executed before the call to the function
>> `f'. This
Hi
this has become more important since it seems I can no longer link a working
gnat1 without
it,
thanks
Iain
> On 4 Dec 2022, at 16:30, Iain Sandoe via Gcc-patches
> wrote:
>
> This fixes a long-standing problem on Darwin where we cannot independently set
> -static-libstdc++ because the flag
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108189
--- Comment #11 from James Hilliard ---
(In reply to Andrew Pinski from comment #1)
> The error is correct at least for C before C23.
Can you clarify where exactly in the C23 specification that this will be
allowed?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108201
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108202
Bug ID: 108202
Summary: [13 Regression] Many new acats fails on 32bit Darwin
hosts.
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
On Wed, Dec 21, 2022 at 11:41:58AM +0800, Kewen.Lin wrote:
> on 2022/12/20 21:19, Segher Boessenkool wrote:
> > Sure, I understand that. What I don't like is the generator program is
> > much too big and unstructured already, and this doesn't help at all; it
> > makes it quite a bit worse even.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108201
Bug ID: 108201
Summary: Warning about conversion from unsigned int to unsigned
int
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
On Thu, Dec 22, 2022 at 11:28:01AM +, Richard Biener wrote:
> On Thu, 22 Dec 2022, Jiufu Guo wrote:
> > To reduce risk, I'm just draft straightforward patches for
> > special cases currently, Like:
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-December/608081.html
> > and this patch.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108199
--- Comment #6 from Andrew Pinski ---
(In reply to Andreas Krebbel from comment #5)
> In:
>
> _1 = src_6(D)->a;
> dst$val_9 = _1;
> _2 = BIT_FIELD_REF ;
> _3 = _2 & 64;
> if (_3 != 0)
There is only 2 accesses going on in the above
Hi!
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 ())
On Thu, 22 Dec 2022, Jose E. Marchesi via Gcc-patches wrote:
> The first instruction scheduler pass reorders instructions in the TRY
> block in a way `b=true' gets executed before the call to the function
> `f'. This optimization is wrong, because `main' calls setjmp and `f'
> is known to call
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108200
Bug ID: 108200
Summary: std::format fails on AIX due to __float128 not being
supported by std::to_chars
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Here is a first patch to add UBSan instrumentation to
assignment, return, initialization of pointers
to variably modified types. This is based on the
other patch I just sent. Separating these should make
reviewing easier.
Here, I did not add tests for function arguments as
this is more
Bootstrapped and regression tested on aarch64-unknown-linux-gnu and
x86_64-pc-linux-gnu - ok to merge?
gcc/ChangeLog:
* tree-ssa-loop-niter.cc (build_popcount_expr): Add IFN support.
gcc/testsuite/ChangeLog:
* g++.dg/tree-ssa/pr86544.C: Add .POPCOUNT to tree scan regex.
Updated to reflect Sphinx revert; I'll commit this once the
cltz_complement patch is merged.
gcc/ChangeLog:
* doc/sourcebuild.texi: Add missing target attributes.
---
diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi
index
On Thu, Nov 24, 2022 at 11:41:31AM +0100, Richard Biener wrote:
> Note we do have CTZ and CLZ
> optabs and internal functions - in case there's a HImode CLZ this
> could be elided. More general you can avoid using the __builtin_
> functions with their fixed types in favor of using IFN_C[TL]Z
Because I want to add another argument to comptypes
and co. for UBSan instrumentation and this then
starts to become a bit unwiedly, here is a patch to
reorganize and simplify this a bit. This can wait
until stage 1. (The cache can be simplified further
by allocating it on the stack, but this
[Public]
Hello,
I have addressed all your comments in this revision of the patch, please find
attached and inlined.
* I have updated all the latencies with Agner's measurements.
* Incorrect pipelines, loads/stores are addressed.
* The double pumped avx512 insns take one cycle for 256 half and
On Thu, 15 Dec 2022, Jason Merrill wrote:
> On 12/15/22 14:31, Patrick Palka wrote:
> > On Thu, 15 Dec 2022, Patrick Palka wrote:
> >
> > > On Thu, 15 Dec 2022, Jason Merrill wrote:
> > >
> > > > On 12/12/22 12:20, Patrick Palka wrote:
> > > > > When instantiating a constrained hidden template
When the following testcase is built with -fschedule-insns in either
x86_64 or aarch64:
#include
#include
#include
jmp_buf ex_buf__;
#define TRY do{ if( !setjmp(ex_buf__) ){
#define CATCH } else {
#define ETRY } }while(0)
#define THROW longjmp(ex_buf__, 1)
int f(int x)
Cupertino Miranda via Gcc-patches writes:
> gentle ping
>
> Cupertino Miranda writes:
>
>>> 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
Cupertino Miranda via Gcc-patches writes:
> gentle ping
>
> Cupertino Miranda writes:
>
>> Hi Jeff,
>>
>> First of all thanks for your quick review.
>> Apologies for the delay replying, the message got lost in my inbox.
>>
>>> On 12/2/22 10:52, Cupertino Miranda via Gcc-patches wrote:
Patches attached to the wrong email - this patch was actually:
On Thu, Dec 22, 2022 at 05:06:13PM +, Andrew Carlotti via Gcc-patches wrote:
> The documentation for the DONE and FAIL macros was incorrectly inserted
> between example code, and a remark attached to that example.
>
> Committed
Patches attached in to the wrong emails - this patch was actually:
On Thu, Dec 22, 2022 at 05:05:51PM +, Andrew Carlotti via Gcc-patches wrote:
> Committed as obvious.
>
> gcc/ChangeLog:
>
> * doc/md.texi: Fix incorrect pxref.
>
> ---
diff --git a/gcc/doc/md.texi b/gcc/doc/md.texi
Richard Earnshaw writes:
> On 14/12/2022 17:00, Richard Earnshaw via Gcc-patches wrote:
>> On 14/12/2022 16:40, Andrea Corallo via Gcc-patches wrote:
>>> Hi Richard,
>>>
>>> thanks for reviewing.
>>>
>>> Richard Earnshaw writes:
>>>
On 28/10/2022 17:40, Andrea Corallo via Gcc-patches
When the following testcase is built with -fschedule-insns in either
x86_64 or aarch64:
jmp_buf ex_buf__;
int f(int x)
{
int arr[] = {1,2,6,8,9,10};
int lo=0;
int hi=5;
while(lo<=hi) {
int mid=(lo+hi)/2;
if(arr[mid]==x) {
THROW;
} else
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108194
--- Comment #6 from Petr Skocik ---
(In reply to Petr Skocik from comment #5)
> (In reply to Andrew Pinski from comment #4)
> > Invalid as mentioned in r13-3135-gfa258f6894801a .
>
> I believe it's still a bug for pre-c2x __typeof.
> While it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108199
--- Comment #5 from Andreas Krebbel ---
In:
_1 = src_6(D)->a;
dst$val_9 = _1;
_2 = BIT_FIELD_REF ;
_3 = _2 & 64;
if (_3 != 0)
src, dst and the BIT_FIELD_REF carry storage order flags which result in either
bswaps being emitted or,
1 - 100 of 197 matches
Mail list logo
