https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103750
Hongtao.liu changed:
What|Removed |Added
Attachment #52031|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103669
Jan Hubicka changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi,
in the testcase we fail to analyze SSA name because flag do_dataflow is set
and thus triggers early exist in analyze_ssa_name. Fixed by disabling
early exits when handling deferred names.
Bootstrapped/regtested x86_64-linux, comitted.
gcc/ChangeLog:
2021-12-20 Jan Hubicka
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103669
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:8d1e342b4afbad77cb92f8057cf6d1e996bfb077
commit r12-6072-g8d1e342b4afbad77cb92f8057cf6d1e996bfb077
Author: Jan Hubicka
Date: Mon
Hi,
I've bootstraped the patch with my GNU-stack fix
(https://github.com/loongson/gcc/pull/62) and --enable-werror-always.
Bootstrap succeeded, but with some warnings:
../../gcc/config/loongarch/loongarch.md:3205:1: warning: operand 0 missing mode?
On Wed, Dec 8, 2021 at 7:32 AM Xionghu Luo wrote:
>
>
>
> On 2021/12/7 20:17, Richard Biener wrote:
> >>> + class loop *coldest_loop = coldest_outermost_loop[loop->num];
> >>> + if (loop_depth (coldest_loop) < loop_depth (outermost_loop))
> >>> +{
> >>> + class loop *hotter_loop =
On Tue, Dec 7, 2021 at 3:16 PM Andrew MacLeod wrote:
>
> On 12/7/21 02:12, Richard Biener wrote:
> > On Mon, Dec 6, 2021 at 7:39 PM Andrew MacLeod wrote:
> >> On
> >> Well, its only does the fill now when there is range info located on an
> >> outgoing edge of the dominator. Its still used,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65642
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81277
Andrew Pinski changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81761
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81761
Andrew Pinski changed:
What|Removed |Added
Known to work||9.1.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91780
--- Comment #13 from Mikael Persson ---
Ah right lifetime
On Sun, 19 Dec 2021, 16:02 Mikael Persson,
wrote:
> Looking at it now, not sure why i didnt.
>
> On Sun, 19 Dec 2021, 14:00 redi at gcc dot gnu.org, <
> gcc-bugzi...@gcc.gnu.org>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367
Bug 54367 depends on bug 102644, which changed state.
Bug 102644 Summary: deduction failure when having default non-type template
parameters that are lambdas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102644
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595
Andrew Pinski changed:
What|Removed |Added
CC||barry.revzin at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102644
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100952
--- Comment #13 from HaoChen Gui ---
Issue for fusion-p10-ldcmpi.c was fixed by r12-1655.
https://gcc.gnu.org/pipermail/gcc-cvs/2021-June/349357.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80488
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38013
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93595
Andrew Pinski changed:
What|Removed |Added
CC||lutztonineubert at gmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97610
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97610
Andrew Pinski changed:
What|Removed |Added
CC||fchelnokov at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101921
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97610
Andrew Pinski changed:
What|Removed |Added
CC||bastien.penavayre at epitech
dot e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96908
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91244
--- Comment #3 from Andrew Pinski ---
>From https://gcc.gnu.org/install/prerequisites.html:
> Note binutils 2.35 or newer is required for LTO to work correctly with GNU
> libtool that includes doing a bootstrap with LTO enabled.
(I added that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91244
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |NEW
See Also|
Hi,
I modified the patch according to David and Segher's advice.
This patch defines a pattern for mffscrni. If the RN is a constant, it can
call
gen_rs6000_mffscrni directly. The "rs6000-builtin-new.def" defines prototype
for builtin arguments.
The pattern "rs6000_set_fpscr_rn" is then
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93459
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103627
--- Comment #4 from Kewen Lin ---
For test.c, even we are on ppc64le P9, it can also get ICE:
extern float *dest;
extern __vector_quad src;
int
foo ()
{
__builtin_mma_disassemble_acc (dest, );
return 0;
}
$ gcc test.c -mcpu=power10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103750
--- Comment #13 from Hongtao.liu ---
Created attachment 52031
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52031=edit
untested patch.
Attached patch can optimize #c0 to
vmovdqu (%rdi), %ymm1
vmovdqu16 32(%rdi),
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103627
--- Comment #3 from Kewen Lin ---
Also failed with r12-0.
I looked into the ICE with -mcpu=power6 -m32 on BE, the direct reason is that
we turn off VSX flag but still leave MMA, when it wants to emit one move for
V16QI it has to use multiple
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91198
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91198
--- Comment #6 from Andrew Pinski ---
void compress(float const * __restrict__ input,
float * __restrict__ output,
int size)
{
float const threshold = 0.5;
int o = 0;
for (int i = 0; i < size;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95792
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93334
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83258
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92937
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85589
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92823
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55610
--- Comment #12 from Eric Gallager ---
(In reply to CVS Commits from comment #11)
> The master branch has been updated by Iain D Sandoe :
>
> https://gcc.gnu.org/g:22a982409323feb203401d345488a5a9c18e6733
>
> commit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92600
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90699
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103750
--- Comment #12 from Hongtao.liu ---
(In reply to Hongtao.liu from comment #11)
> (In reply to Thiago Macieira from comment #6)
> > It got worse. Now I'm seeing:
> >
> > .L807:
> > vmovdqu16 (%rsi), %ymm2
> > vmovdqu16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90524
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> aarch64 error message is good:
> :2:1: error: pragma or attribute 'target("foobar")' is not valid
> 2 | __attribute__ ((target ("foobar"))) void foo () { }
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90524
Andrew Pinski changed:
What|Removed |Added
Target||x86_64-linux-gnu
--- Comment #3 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90524
Andrew Pinski changed:
What|Removed |Added
Summary|attribute name and argument |[10/11/12 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103750
--- Comment #11 from Hongtao.liu ---
(In reply to Thiago Macieira from comment #6)
> It got worse. Now I'm seeing:
>
> .L807:
> vmovdqu16 (%rsi), %ymm2
> vmovdqu16 32(%rsi), %ymm3
> vpcmpuw $6, %ymm0, %ymm2,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90760
Andrew Pinski changed:
What|Removed |Added
CC||guillaume.bertholon@hotmail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90470
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90487
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90368
--- Comment #1 from Andrew Pinski ---
I think this was fixed in GCC 11 by r11-7878-gbe080b17271cfbe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88874
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98648
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101017
Andrew Pinski changed:
What|Removed |Added
Known to fail||6.1.0, 7.1.0, 8.1.0, 9.1.0
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98468
Hongtao.liu changed:
What|Removed |Added
CC||crazylht at gmail dot com
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98648
--- Comment #6 from Hongtao.liu ---
Fixed by r12-6071-g19dcecd963295b02b96c8cac57933657dbe3234a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86710
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103750
--- Comment #10 from Hongtao.liu ---
(In reply to Uroš Bizjak from comment #9)
> (In reply to Thiago Macieira from comment #0)
> > Testcase:
> ...
> > The assembly for this produces:
> >
> > vmovdqu16 (%rdi), %ymm1
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86267
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86488
Andrew Pinski changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98468
--- Comment #5 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:19dcecd963295b02b96c8cac57933657dbe3234a
commit r12-6071-g19dcecd963295b02b96c8cac57933657dbe3234a
Author: liuhongt
Date: Wed Dec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68384
Andrew Pinski changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86442
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86437
--- Comment #4 from Andrew Pinski ---
I tried "-Ofast -fmax-stack-var-size=2096" and I get:
_38 = __builtin_malloc (848);
Without the max-stack-var-size option, I get:
real(kind=8) A.22[106];
Even with " -fmax-stack-var-size=2096
On Thu, Dec 16, 2021 at 1:59 PM liuhongt wrote:
>
> Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
> Ok for trunk?
Pushed to trunk.
>
> gcc/ChangeLog:
>
> PR target/98468
> * config/i386/sse.md (*bit_and_float_vector_all_ones): New
> pre-reload splitter.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86016
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86345
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #3 from
On Linux/x86_64,
6bcb6ed5a44b6f271891246ef7ae568bfdc14e9c is the first bad commit
commit 6bcb6ed5a44b6f271891246ef7ae568bfdc14e9c
Author: Matthias Kretz
Date: Wed Dec 15 09:45:06 2021 +0100
c++: don't ICE on NAMESPACE_DECL inside FUNCTION_DECL
caused
FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100801
Andrew Pinski changed:
What|Removed |Added
Summary|Aggressive loop |[9/10/11/12 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69471
--- Comment #21 from H.J. Lu ---
*** Bug 42444 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42444
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36748
Andrew Pinski changed:
What|Removed |Added
Known to fail||4.7.1
--- Comment #4 from Andrew Pinski
If it does not contain any files, then there is no point compiling it.
Skipping this saves some milliseconds and ~650 bytes in libgphobos.a.
---
libphobos/configure.ac| 1 +
libphobos/libdruntime/Makefile.am | 2 ++
.../libdruntime/config/x86/switchcontext.S
On musl, linking against libphobos fails because it requires ucontext
but is not explicitly linked against it. This is caused by configure
assuming that it is implemented in assembly, but it is actually not
implemented. This silently works on other libcs because context API does
not require an
Hi Thomas,
> OK, and thanks for the patch!
Thanks for the review, committed a slightly amended patch as
220b9bdfe8faebdd2aea0ab7cea81c162d42d8e0 with underflow control support added.
FX
ieee.patch
Description: Binary data
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103194
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Hi Thomas,
> I am not sure the logic is correct for POWER (old style) where we have
> a 16-byte long double made up from two 8-byte doubles, which is not
> __float128 (IFmode)
As written, the patch should be a no-op for existing platforms. I know about
the ppc double-double "long double" type,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69690
--- Comment #2 from Andrew Pinski ---
The handling of the incompatible of pg and fomit-frame-pointer should be moved
to opts.c out of the spec really.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629
Andrew Pinski changed:
What|Removed |Added
Summary|Possible miscompilation |[11/12 Regression] Possible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629
--- Comment #18 from Andrew Pinski ---
Could Visibility not being applied correctly to lambdas but does that matter?
Snapshot gcc-12-20211219 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20211219/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
From: Andrew Pinski
With the recent PHI-OPT patch for line numbers, I had missed this
testcase was now failing. The uninitialized warning was there
before my recent patch, just was on the wrong line. The testcase
had added an xfail in r12-4698-gf6d012338 (though a bug report was
not filed to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103766
--- Comment #12 from hubicka at kam dot mff.cuni.cz ---
> Even trying to find a Fortran testsuite friendly version is hard because the
> issue can only happen with print, I tried even doing internal write to a
> string
> it is passing without
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103669
--- Comment #2 from Jan Hubicka ---
Created attachment 52030
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52030=edit
Patch in testing
The problem here is a mixup with do_dataflow flag which prevents the name from
being analyzed. I am
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84864
--- Comment #8 from Andrew Pinski ---
>From my notes of the duplicated bug:
clang does not use negative line numbers:
:2147483648:9: warning: A1 [-W#pragma-messages]
But MSVC does:
(-2147483648): warning C4081: expected '('; found 'string'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84864
Andrew Pinski changed:
What|Removed |Added
CC||jg at jguk dot org
--- Comment #7 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90477
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103766
--- Comment #11 from Andrew Pinski ---
(In reply to Iain Sandoe from comment #7)
> (In reply to Jan Hubicka from comment #6)
>
> > I would welcome a testuite friendly version of the fortran testcase
>
> Both Andrew and I failed to make a C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103766
Jan Hubicka changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
Hi,
when adding support for static chain and return slot flags I forgot to update
early exit condition in modref_merge_call_site_flags. This yields to wrong
code as demonstrated by the Fortran testcase attached to PR (which I hope
someone will help me to turn into testuite one).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103766
--- Comment #9 from CVS Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:fcbf94a5be9e0c1ecad92da773a6632b86b7f70a
commit r12-6067-gfcbf94a5be9e0c1ecad92da773a6632b86b7f70a
Author: Jan Hubicka
Date: Sun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103766
--- Comment #8 from hubicka at kam dot mff.cuni.cz ---
> > I would welcome a testuite friendly version of the fortran testcase
>
> Both Andrew and I failed to make a C reproducer - what about just taking the
> -fdump-tree-gimple, as input would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103766
--- Comment #7 from Iain Sandoe ---
(In reply to Jan Hubicka from comment #6)
> I would welcome a testuite friendly version of the fortran testcase
Both Andrew and I failed to make a C reproducer - what about just taking the
This patch fixes a memory leak in the pass manager. In the existing code,
the m_name_to_pass_map is allocated in pass_manager::register_pass_name, but
never deallocated. This is fixed by adding a deletion in
pass_manager::~pass_manager. Moreover the string keys in m_name_to_pass_map are
all
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103418
--- Comment #14 from CVS Commits ---
The releases/gcc-11 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:57b51b8bae4c2ecec3281929f57e4a6a0e6f9ea0
commit r11-9404-g57b51b8bae4c2ecec3281929f57e4a6a0e6f9ea0
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103770
Andrew Pinski changed:
What|Removed |Added
Summary|ICE related to VLA |[11 Regression] ICE related
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99188
Pavel Mayorov changed:
What|Removed |Added
CC||pmayorov at cloudlinux dot com
---
Hi FX,
Since support for target aarch64-apple-darwin has been submitted for review,
it’s time to submit the Fortran part, i.e. enabling IEEE support on that target.
The patch has been in use now for several months, in a developer branch shipped
by some distros on macOS (including
1 - 100 of 174 matches
Mail list logo
