https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89585
Andrew Pinski changed:
What|Removed |Added
Known to fail||7.4.0, 8.3.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107732
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107712
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68097
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106649
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107444
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107624
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107676
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107645
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107206
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.3
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107492
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107305
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100525
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106140
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106302
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100972
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106235
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107618
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89430
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99671
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107581
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107599
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107363
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107584
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53562
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |7.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24021
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107389
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106644
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107550
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102614
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32193
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107342
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106721
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.3
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106045
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.4
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99966
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93917
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107486
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106449
Andrew Pinski changed:
What|Removed |Added
Known to fail||12.1.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107510
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107121
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.3
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106643
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105364
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96688
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89653
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107903
Bug ID: 107903
Summary: new test case gcc.dg/analyzer/file-CWE-1341-example.c
in r13-4218-g9ada45967b4cf5 has excess errors
Product: gcc
Version: 13.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68180
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64410
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |5.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88676
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107819
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26016
Andrew Pinski changed:
What|Removed |Added
CC||pskocik at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88131
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70718
Andrew Pinski changed:
What|Removed |Added
Keywords||internal-improvement
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70718
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_option_override): Fix comment
wording.
---
Just stumbled on this one looking at the output of that sed script. The
script itself was fine, the original comment was to blame.
---
gcc/config/riscv/riscv.cc | 2 +-
1 file changed, 1
I am part of a team working on a COBOL front end for GCC.
By reverse engineering other front ends, I learned, some months ago, how
to create a function_decl GENERIC node that is the root of a GENERIC tree
describing an entire function.
By calling the routine cgraph_node::finalize_function()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107819
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
[temp.res.general]/3 says, in a note, "the usual qualified name lookup
([basic.lookup.qual]) applies even in the presence of typename". Thus
when resolving a TYPENAME_TYPE, it seems we shouldn't be looking past
non-type members.
This patch fixes this by passing want_type=false instead of =true
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107902
Bug ID: 107902
Summary: std::sort isn't usable on 16-bit targets
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107901
--- Comment #2 from Jonathan Wakely ---
Or simply:
--- a/libstdc++-v3/include/std/format
+++ b/libstdc++-v3/include/std/format
@@ -3034,6 +3034,7 @@ namespace __format
return std::forward<_Visitor>(__vis)(_M_val._M_ll);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107901
Jonathan Wakely changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107901
Bug ID: 107901
Summary: std::format isn't usable on 16-bit targets
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107773
Patrick Palka changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107899
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107900
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
On Mon, Mar 7, 2022 at 6:06 AM Jakub Jelinek via Gcc-patches
wrote:
>
> Hi!
>
> Like in r10-7215-g700d4cb08c88aec37c13e21e63dd61fd698baabc 2 years ago,
> I've run
> grep -v 'long long\|optab optab\|template template\|double double'
> *.{[chS],cc} */*.{[chS],cc} *.def config/*/* 2>/dev/null |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101733
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:2b0ae7fb91f64fb005abf7d7903fd4c0764bb45c
commit r13-4380-g2b0ae7fb91f64fb005abf7d7903fd4c0764bb45c
Author: Jason Merrill
Date:
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
Usually a requirement starting with 'typename' is a type-requirement, but it
might be a simple-requirement such as a functional cast to a typename-type.
PR c++/101733
gcc/cp/ChangeLog:
* parser.cc (cp_parser_requirement):
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
Some clang folks mailed me asking about being less permissive about
'concept bool', so let's bump it up from pedwarn to permerror.
gcc/cp/ChangeLog:
* parser.cc (cp_parser_decl_specifier_seq): Change 'concept bool'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104688
--- Comment #27 from Peter Cordes ---
(In reply to Alexander Monakov from comment #26)
> Sure, the right course of action seems to be to simply document that atomic
> types and built-ins are meant to be used on "common" (writeback) memory
Hi Adrian,
Again thanks for working on this and getting it into a suitable state for
posting.
It’s a good idea to CC relevant maintainer(s) on patches [see MAINTAINERS] and
I’d welcome cc on any coroutines ones (it’s easy to miss a patch otherwise).
> On 28 Nov 2022, at 11:55, Adrian Perl via
On 28/11/22 19:35, Jonathan Wakely wrote:
On Mon, 28 Nov 2022 at 06:07, François Dumont via Libstdc++
mailto:libstdc%2b...@gcc.gnu.org>> wrote:
This patch is fixing those tests:
20_util/to_chars/float128_c++23.cc
std/format/formatter/requirements.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107900
Bug ID: 107900
Summary: Select type with intrinsic type inside associate
causes ICE / Segmenation fault
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107772
--- Comment #5 from Avi Kivity ---
It indeed generates better code. However, it requires that I duplicate the
function body, which can be hard at times (consider f == std::transform and "if
(*b != 0) { *b = g(*b); }" as a lambda input.
Here we're crashing when using an explicit specialization of a function
template with trailing requirements ultimately because decls_match
(called indirectly from register_specialization) returns false since the
template has trailing requirements whereas the specialization doesn't.
In
From: Andrew Pinski
There was a small typo where Also was done
twice. The second also should have been
handled. This fixes that.
Committed as obvious after a build.
gcc/ChangeLog:
* match.pd ((A / (1 << B)) -> (A >> B).):
Fix comment.
---
gcc/match.pd | 2 +-
1 file changed,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104688
--- Comment #26 from Alexander Monakov ---
Sure, the right course of action seems to be to simply document that atomic
types and built-ins are meant to be used on "common" (writeback) memory, and no
guarantees can be given otherwise, because it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105119
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Dear all,
as reported, the Fortran standard requires all actual argument
expressions to be evaluated (e.g. F2018:15.5.3).
There were two cases for intrinsic MERGE where we failed to do so:
- non-constant mask; Steve provided the patch
- constant scalar mask; we need to be careful to simplify
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105119
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105137
Andrew Pinski changed:
What|Removed |Added
Target||x86_64-linux-gnu
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107882
--- Comment #2 from Tim Lange ---
Created attachment 53979
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53979=edit
patch for pr107882
I think the assertion here uncovered a bug. Currently, if the OTHER parameter
of
On 11/10/22 07:37, Lin Sinan via Gcc-patches wrote:
The motivation of this patch is to correct the wrong estimation of the number
of instructions needed for loading a 64bit constant in rv32 in the current cost
model(riscv_interger_cost). According to the current implementation, if a
On Mon, 28 Nov 2022, Jeff Law wrote:
> > Given the false negatives how about getting a bit stricter and also
> > checking there's nothing following the XORI instruction, like here?
> >
> > It might be an overkill to have a check both for the sequence and for the
> > absence of ANDI or SEXT.W
On Mon, 28 Nov 2022 11:15:01 PST (-0800), gcc-patches@gcc.gnu.org wrote:
>
>
> On 11/24/22 00:43, Sinan wrote:
>>> The motivation of this patch is to correct the wrong estimationÂ
>>>of
 the number of instructions needed for loading a 64bit constantÂ
in
 rv32Â
On 11/24/22 00:43, Sinan wrote:
The motivation of this patch is to correct the wrong estimation of
the number of instructions needed for loading a 64bit constant in
rv32 in the current cost model(riscv_interger_cost). According to
the current implementation, if a constant requires more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99576
--- Comment #12 from Adrian Perl ---
I have sent the patch and tests to gcc-patc...@gcc.gnu.org
Thanks for the guidance
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107879
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104688
--- Comment #25 from Peter Cordes ---
(In reply to Alexander Monakov from comment #24)
>
> I think it's possible to get UC/WC mappings via a graphics/compute API (e.g.
> OpenGL, Vulkan, OpenCL, CUDA) on any OS if you get a mapping to device
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105127
--- Comment #2 from Sam Darwin ---
yes, reported: https://cygwin.com/pipermail/cygwin/2022-January/250693.html
I don't know where the bug originates, in gcc or cygwin. If an expert in gcc
could submit a fix to cygwin or vice versa.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107819
--- Comment #14 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:07b9bcc1d1484f8f1c850ff14db678fb6b1e4d36
commit r13-4375-g07b9bcc1d1484f8f1c850ff14db678fb6b1e4d36
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104688
--- Comment #24 from Alexander Monakov ---
(In reply to Peter Cordes from comment #23)
> But at least on Linux, I don't think there's a way for user-space to even
> ask for a page of WT or WP memory (or UC or WC). Only WB memory is easily
>
On Mon, Nov 28, 2022 at 6:58 PM Segher Boessenkool
wrote:
>
> On Mon, Nov 28, 2022 at 09:42:05AM +0100, Richard Biener wrote:
> > Since the function seems to be allowed to fail the patch looks
> > reasonable - still I wonder
> > what the "fallback" for a MODE_CC style compare-and-branch is?
On Fri, 18 Nov 2022 09:01:08 PST (-0800), Palmer Dabbelt wrote:
On Thu, 17 Nov 2022 22:59:08 PST (-0800), Kito Cheng wrote:
Wait, what's Xgnuzihintpausestate???
I just made it up, it's defined right next to the name like those
profile extensions are. I figured that's the most RISC-V way to
I forgot to add the patch but as you already made another feedback I'll
clean my patch first.
On 28/11/22 19:43, François Dumont wrote:
On 28/11/22 11:21, Jonathan Wakely wrote:
On Mon, 28 Nov 2022 at 10:10, Jonathan Wakely wrote:
On Mon, 28 Nov 2022 at 06:07, François Dumont via
On 28/11/22 11:21, Jonathan Wakely wrote:
On Mon, 28 Nov 2022 at 10:10, Jonathan Wakely wrote:
On Mon, 28 Nov 2022 at 06:07, François Dumont via Libstdc++
mailto:libstdc%2b...@gcc.gnu.org>> wrote:
This patch is fixing those tests:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107896
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107896
--- Comment #3 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:2200b7054638bbf157192a4dca23886dd420becb
commit r13-4374-g2200b7054638bbf157192a4dca23886dd420becb
Author: Richard Biener
Date:
The following avoids ICEing for V2SI -> DImode vec_unpacks_lo.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR tree-optimization/107896
* tree-vect-stmts.cc (supportable_widening_operation):
Handle non-vector mode intermediate mode.
---
101 - 200 of 366 matches
Mail list logo