https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105940
Bug ID: 105940
Summary: suggested_unroll_factor applying place looks wrong
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
a8, a8, 0, 4
beqia8, 4, .L4
l32ra8, .LC3
callx8 a8
.L4:
movi.n a10, 0
l32ra8, .LC4
callx8 a8
.size main, .-main
.global x
.data
.align 4
.type x, @object
.size x, 4
x:
.byte 32
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105817
tonnyl at nvidia dot com changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105939
--- Comment #1 from Eric Gallager ---
Oh, one more; I updated the testcase so it's now:
$ cat icculus_twitter_thread.c
#include
int main(void) {
int x = 0;
do printf("%d\n", x++); while (x < 10);
return 0;
}
const const const
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105939
Bug ID: 105939
Summary: "warning: anonymous struct declared inside parameter
list will not be visible outside of this definition or
declaration" should have a warning flag attached
Thank you for the review Andi.
Yes, the corresponding reader change is
@@ -15671,8 +15673,9 @@ module_state::read_location (bytes_in ) const
if (range.m_start == UNKNOWN_LOCATION)
range.m_start = locus;
range.m_finish = read_location (sec);
+ unsigned
Eugene Rozenfeld via Gcc-patches writes:
> {
> diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
> index d1dc73724d1..5ed6b7b0f94 100644
> --- a/gcc/cp/module.cc
> +++ b/gcc/cp/module.cc
> @@ -15587,6 +15587,8 @@ module_state::write_location (bytes_out ,
> location_t loc)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105753
--- Comment #4 from Andrew Pinski ---
g:3ba781d3b5c8efadb60866c9743b657e8f0eb222
: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
building the nxptx-none offload compiler with the just built gcc-12 from the
branch 20220612 ICEs in:
[...]
2204622
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105753
Filip Hejsek changed:
What|Removed |Added
Known to fail||12.1.0
Known to work|
Snapshot gcc-13-20220612 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20220612/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105937
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-reduction
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104871
--- Comment #1 from CVS Commits ---
The master branch has been updated by Iain D Sandoe :
https://gcc.gnu.org/g:add1adaa17a294ea25918ffb4fdd40f115362632
commit r13-1058-gadd1adaa17a294ea25918ffb4fdd40f115362632
Author: Simon Wright
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105937
--- Comment #1 from Andrew Pinski ---
Note your example no longer compiles on the trunk of GCC as it requires to add:
#include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105937
Bug ID: 105937
Summary: [12] Regression with maybe-uninitialized
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105922
Andrew Pinski changed:
What|Removed |Added
Summary|AArch64 SVE instruction |autovectorizer does not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105927
Uroš Bizjak changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ubizjak at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105927
Uroš Bizjak changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
On Do, Jun 9 2022 at 13:40:06 -0400, David Malcolm
wrote:
On Thu, 2022-06-09 at 16:49 +0200, Tim Lange wrote:
> On Mi, Jun 8 2022 at 11:12:52 -0400, David Malcolm
wrote:
> > On Wed, 2022-06-08 at 01:42 +0200, Tim Lange wrote:
> >
> > Hi Dave,
Hi Tim; various responses inline
Hi,
On Fri, Jun 10 2022, Jan Hubicka wrote:
> Hi,
> this patch prevents ipa-prop from propagating aggregates when load is
> volatile. Martin, does this look OK? It seem to me that ipa-prop may
> need some additional volatile flag checks.
load_from_unmodified_param_or_agg checks for it,
On 6/10/2022 3:14 AM, Richard Sandiford via Gcc-patches wrote:
Several existing internal functions map directly to an instruction
defined in target-insns.def. This patch makes it easier to define
more such functions in future.
This should help to reduce cut-&-paste, but more importantly, it
On 6/10/2022 3:13 AM, Richard Sandiford via Gcc-patches wrote:
internal-fn.c has quite a few functions that simply map the result
of the call to an instruction's output operand (if any) and map
each argument to an instruction's input operand, in order.
This patch adds a single function for
On 6/3/2022 11:27 AM, Roger Sayle wrote:
Hi Richard,
Here's a revised version of my patch incorporating both your suggestions.
The algorithm now uses two worklist vectors, and pointers to them,
alternating between them on each iteration, which allows the code to
handle an arbitrary number of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105932
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
On 6/5/2022 7:12 AM, Roger Sayle wrote:
This patch resolves PR tree-optimization/105835, which is a code quality
(dead code elimination) regression at -O1 triggered/exposed by a recent
change to canonicalize X&-Y as X*Y. The new (shorter) form exposes some
missed optimization opportunities
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105936
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-reduction
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105936
Andrew Pinski changed:
What|Removed |Added
Keywords|needs-reduction |inline-asm
Summary|[10
On Fri, Jun 10, 2022 at 9:27 PM Jakub Jelinek wrote:
>
> Hi!
>
> Another regression caused by my recent patch.
>
> This time because define_insn_and_split only requires that the
> constant mask is const_int_operand. When it was only SImode,
> that wasn't a problem, HImode neither, but for DImode
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105930
--- Comment #10 from Linus Torvalds ---
(In reply to Roger Sayle from comment #7)
> Investigating. Adding -mno-stv the stack size reduces from 2612 to 428 (and
> on godbolt the number of assembler lines reduces from 6952 to 6203).
So now that
On 6/9/2022 1:52 AM, Tamar Christina via Gcc-patches wrote:
Hi All,
When lowering COMPLEX_EXPR we currently emit two VEC_EXTRACTs. One for the
lowpart and one for the highpart.
The problem with this is that in RTL the lvalue of the RTX is the only thing
tying the two instructions together.
On 6/6/2022 7:50 AM, Roger Sayle wrote:
This patch fixes both ICE regressions PR middle-end/105853 and
PR target/105856 caused by my recent patch to expand small const structs
as immediate constants. That patch updated code generation in three
places: two in expr.cc that call
On Sun, Jun 12, 2022 at 12:38 PM David Malcolm via Gcc wrote:
>
> On Sat, 2022-06-11 at 02:35 +0200, Eric Botcazou wrote:
> > > Hope this is helpful; please let me know if you see any mistakes,
> > > or if
> > > there's room for improvement
> >
> > Nice work! In the "inside cc1" chapter, I think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105936
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |10.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105931
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2022-06-12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105931
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic,
|
On Sat, 2022-06-11 at 02:35 +0200, Eric Botcazou wrote:
> > Hope this is helpful; please let me know if you see any mistakes,
> > or if
> > there's room for improvement
>
> Nice work! In the "inside cc1" chapter, I think that IR is usually
> meant for
> "Intermediate Representation" rather than
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105930
--- Comment #9 from Linus Torvalds ---
Looks like STV is "scalar to vector" and it should have been disabled
automatically by the -mno-avx flag anyway.
And the excessive stack usage was perhaps due to GCC preparing all those stack
slots for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105916
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105930
--- Comment #8 from Linus Torvalds ---
(In reply to Roger Sayle from comment #7)
> Investigating. Adding -mno-stv the stack size reduces from 2612 to 428 (and
> on godbolt the number of assembler lines reduces from 6952 to 6203).
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105916
--- Comment #1 from David Malcolm ---
Thanks for filing this.
Reproducable with trunk. On trunk I also see similar behavior with the new
SARIF output format via options:
-fdiagnostics-format=sarif-stderr
-fdiagnostics-format=sarif-file
On 6/10/2022 4:57 AM, Eric Botcazou via Gcc-patches wrote:
Hi,
gimple_set_location is mostly invoked on newly built GIMPLE statements, so
their location is UNKNOWN_LOCATION and setting it will clobber the warning
data of the passed location, if any.
Tested on x86-64/Linux, OK for mainline
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105936
Bug ID: 105936
Summary: internal compiler error: in move_insn, at
haifa-sched.c:5463
Product: gcc
Version: 9.4.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105935
Bug ID: 105935
Summary: libgfortran build fails if HAVE_VSNPRINTF test fails
Product: gcc
Version: 10.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Hey
I’m Olive and I run a file sharing service called SendBig.com where you can
send files up to 30GB for Free with amazing features available.
I stumbled upon your website https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94138
, and I just have to say: WOW!
I had a quick proposal, I was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105747
--- Comment #9 from David Binderman ---
(In reply to David Binderman from comment #8)
> (In reply to David Binderman from comment #7)
> > Created attachment 53119 [details]
> > C source code
> >
> > Another one. Over 15 minutes this time.
>
>
On 2022/06/12 16:51, Max Filippov wrote:
This patch is whitespace-damaged. Please resend.
oh, sorry.
reposted as zip in attachment due to avoiding damage.<>
On Sat, Jun 11, 2022 at 11:43 PM Takayuki 'January June' Suwa
wrote:
>
> No need to describe the "false side" conditional insn patterns anymore.
>
> gcc/ChangeLog:
>
> * config/xtensa/xtensa-protos.h (xtensa_emit_branch):
> Remove the first argument.
>
This patch offers several insn-and-split patterns for bitwise AND with
register and constant that cannot fit into a "MOVI Ax, simm12" instruction,
but can be represented as:
i. 1's least significant N bits and the others 0's (17 <= N <= 31)
ii. 1's most significant N bits and the others 0's
In Xtensa ISA, there is no single machine instruction that calculates unary
bitwise negation, but a few similar fused instructions are exist:
"BALL Ax, Ay, label" // if ((~Ax & Ay) == 0) goto label;
"BNALL Ax, Ay, label" // if ((~Ax & Ay) != 0) goto label;
These instructions have never
No need to describe the "false side" conditional insn patterns anymore.
gcc/ChangeLog:
* config/xtensa/xtensa-protos.h (xtensa_emit_branch):
Remove the first argument.
(xtensa_emit_bit_branch): Remove it because now called only from the
output statement of
This patch introduces funnel shifter utilization, and rearranges existing
"per-byte shift" insn patterns.
gcc/ChangeLog:
* config/xtensa/predicates.md (logical_shift_operator,
xtensa_shift_per_byte_operator): New predicates.
* config/xtensa/xtensa-protos.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105930
Roger Sayle changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
52 matches
Mail list logo
