https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106736
--- Comment #17 from Kewen Lin ---
(In reply to Arseny Solokha from comment #16)
> (In reply to Kewen Lin from comment #15)
> > Thanks for reporting, confirmed. The function
> > rs6000_opaque_type_invalid_use_p only handles gassign, this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108272
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2023-01-03
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108240
Kewen Lin changed:
What|Removed |Added
Target|poiwerpc|powerpc
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108240
--- Comment #2 from Kewen Lin ---
Well, there are two issues here:
1) the ICE itself, it's independent of option powerpc64 handling, without the
culprit commit r13-4894 but with an explicit option -m64, the ICE is still
reproducible. So this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106736
--- Comment #16 from Arseny Solokha ---
(In reply to Kewen Lin from comment #15)
> Thanks for reporting, confirmed. The function
> rs6000_opaque_type_invalid_use_p only handles gassign, this failure shows
> another usage with asm, so we need to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108272
Bug ID: 108272
Summary: [13 Regression] ICE in gen_movxo, at
config/rs6000/mma.md:339
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108185
Kito Cheng changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108271
--- Comment #2 from JuzheZhong ---
(In reply to Andrew Pinski from comment #1)
> More likely there should be a generic scheduling model that handles RVV too
> instead of a cost issue ...
OK. This issue should be fixed after I support all RVV
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108271
--- Comment #1 from Andrew Pinski ---
More likely there should be a generic scheduling model that handles RVV too
instead of a cost issue ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108271
Bug ID: 108271
Summary: Missed RVV cost model
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106736
--- Comment #15 from Kewen Lin ---
(In reply to Arseny Solokha from comment #14)
> W/ gcc 13.0.0 20221225 snapshot (g:febb58d28bfa4b544ec7ffec2d61f46d25205ff0)
> I still get this ICE when compiling
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108240
Kewen Lin changed:
What|Removed |Added
Status|NEW |ASSIGNED
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108185
--- Comment #3 from jiawei ---
(In reply to Kito Cheng from comment #2)
> It seems right to me?
Yes, It have the same behavior with clang, but it could generate better
assemble code like:
vl1re8.vv24,0(a0)
addi a4,a1,800
vs1r.v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108270
JuzheZhong changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108270
Bug ID: 108270
Summary: un-optimal vsetvl for multi-loop if avl is 0 ~ 31
immediate
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108269
--- Comment #3 from Andrew Pinski ---
__PRETTY_FUNCTION__ is also a GCC extension too so ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108250
--- Comment #10 from Sam James ---
Both Arsen and I gave it a go and it doesn't seem to make a difference either
way (it doesn't induce miscompilation with the revert, and it doesn't fix
miscompilation without the revert).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108269
--- Comment #2 from Andrew Pinski ---
Note this is just a problem with __PRETTY_FUNCTION__/__func__ and not an ABI
issue as it is done correctly for the mangling.
So it is just a minor issue dealing with debugging really because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108269
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105216
--- Comment #16 from Hongtao.liu ---
(In reply to Andrew Pinski from comment #15)
> Might be interesting to test it again to see if it has been fixed on the
> trunk.
The regression is still there.
gcc version 13.0.0 20230102 (experi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108269
Bug ID: 108269
Summary: Incorrect __PRETTY_FUNCTION__ with std::array in
C++20 NTTP literal
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108268
Andrew Pinski changed:
What|Removed |Added
Keywords||build
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108268
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |13.0
Priority|P3
=/builddir/build/BUILD/gcc-13.0.0-20230102/obji/usr/nvptx-none/bin
--
target nvptx-none --enable-as-accelerator-for=ppc64le-redhat-linux
--enable-languages=c,c++,fortran,lto --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=
http://bugzilla.redhat.com/bugzilla --enable-checking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98112
James Y Knight changed:
What|Removed |Added
CC||foom at fuhm dot net
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
--- Comment #13 from Jürgen Reuter ---
(In reply to Iain Sandoe from comment #12)
.
>
> Next, I guess I'll pick up the xc 14.2 release.
Sorry, my bad, I misplaced the position of the argument
BOOT_CFLAGS, I erroneously (like for configure,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108267
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108267
Andrew Pinski changed:
What|Removed |Added
Severity|normal |blocker
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108267
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |13.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108267
Bug ID: 108267
Summary: [13 Regression] Bootstrap failure on aarch64-linux
since r13-4953
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Got it, I'll email that account and hopefully get things sorted out then --
thanks Andrew and Happy New Year to you!
On Mon, Jan 2, 2023 at 1:33 PM Andrew Pinski wrote:
> On Mon, Jan 2, 2023 at 10:21 AM Gavin Ray wrote:
> >
> > I tried but it won't allow me to create an issue on the bugzilla,
On Mon, Jan 2, 2023 at 10:21 AM Gavin Ray wrote:
>
> I tried but it won't allow me to create an issue on the bugzilla, it says
> "account creation is not allowed at this time"
Directly from https://gcc.gnu.org/bugzilla/createaccount.cgi :
"Because of spam, account creation through this form is
I tried but it won't allow me to create an issue on the bugzilla, it says
"account creation is not allowed at this time"
On Mon, Jan 2, 2023 at 1:17 PM Andrew Pinski wrote:
> Please file a bug to bugzilla. With attaching the source there.
> This list is for automated emails from bugzilla really
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108235
--- Comment #5 from Jonathan Wakely ---
tzdb.cc doesn't need atomics, it can just work with a mutex. I'm still on
holiday until tomorrow though.
Please file a bug to bugzilla. With attaching the source there.
This list is for automated emails from bugzilla really and most folks
are not tracking the list.
Thanks,
Andrew
On Mon, Jan 2, 2023 at 10:16 AM Gavin Ray via Gcc-bugs
wrote:
>
> Hit the following ICE today, just sharing here to be
Hit the following ICE today, just sharing here to be helpful:
https://gcc.godbolt.org/z/advKKxK43
during RTL pass: final
: In member function 'void Stack::push(int)':
:20:3: internal compiler error: in gen_inlined_subroutine_die, at
dwarf2out.cc:25002
20 | }
| ^
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108235
--- Comment #4 from John David Anglin ---
Working on a patch to add support for sync libfuncs.
Downside is one needs to add -fno-sync-libcalls to generate calls for
libatomic. I think the HP implementations of pthread_mutex_lock and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108260
--- Comment #1 from Jonathan Wakely ---
(In reply to rhalbersma from comment #0)
> I'm a happy user of std::views::zip in gcc-latest but AFAICS the feature
> test macro __cpp_lib_ranges_zip is not yet defined, neither in ,
> , , nor in . This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
--- Comment #12 from Iain Sandoe ---
with Xcode 14.1 CLT and the macOS13 SDK, the build fails without the
work-around and works for this:
time nice make -j10 BOOT_CFLAGS="-O2 -g -Wno-error=deprecated-declarations"
>b.txt 2>e.txt
(jftr)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108047
Andrew Pinski changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108266
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87832
--- Comment #13 from CVS Commits ---
The master branch has been updated by Alexander Monakov :
https://gcc.gnu.org/g:ec1db9017939bb8289c9bd63aace66c0f3957ecd
commit r13-4956-gec1db9017939bb8289c9bd63aace66c0f3957ecd
Author: Alexander Monakov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108266
Jakub Jelinek changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108266
Bug ID: 108266
Summary: [13 Regression] ICE during
cxx_eval_constant_expression on IMPLICIT_CONV_EXPR
since r13-4564
Product: gcc
Version: 13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108265
Bug ID: 108265
Summary: chrono::hh_mm_ss can't be constructed from unsigned
durations
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108264
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
--- Comment #11 from Iain Sandoe ---
at what stage is it failing?
(and with what error)
.. when I las tried this with the macOS13 SDK it dod work .. I will try to fit
a test run in sometime (stuff is tied up with other testing right now)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
--- Comment #10 from Jürgen Reuter ---
(In reply to Iain Sandoe from comment #9)
> (I don't have a macOS13 setup yet, limited hardware available here)
>
> ... so, if it is not fixed in the Xcode 14.x releases, we'll have to work
> around it in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108264
--- Comment #1 from Jakub Jelinek ---
store_expr is called with target (subreg/s/u:SI (reg/v:DI 66 [ x+-4 ]) 4) where
the mode is still correct...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108264
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108264
Bug ID: 108264
Summary: [11/12/13 Regression] ICE compiling guacamole-server
on s390x-linux
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108261
Iain Sandoe changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108263
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=108110
Sergei Trofimovich changed:
What|Removed |Added
CC||slyfox at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
Iain Sandoe changed:
What|Removed |Added
Target Milestone|--- |13.0
--- Comment #9 from Iain Sandoe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108182
--- Comment #2 from Iain Sandoe ---
computing the multilib_os_dir in the language driver is not going to be
easy/reliably correct, since that code is called very early and the specs
applied later could well modify the command line options.
On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107568
--- Comment #8 from Jürgen Reuter ---
What is the status of this problem? I checked with Darwin 22.2 and XCode 14.2,
and the problem still persists with the Git master, cf. below. Is there a
workaround for the moment? Will this be resolved
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108183
Iain Sandoe changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108110
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108259
Iain Sandoe changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108263
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|--- |13.0
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108263
Bug ID: 108263
Summary: [13 Regression] ICE building Linux kernel on ppc64le
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108183
Iain Sandoe changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107612
Iain Sandoe changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108202
Iain Sandoe changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108202
--- Comment #2 from CVS Commits ---
The master branch has been updated by Iain D Sandoe :
https://gcc.gnu.org/g:8385088039f58a1d403cbb0792105236d240de85
commit r13-4952-g8385088039f58a1d403cbb0792105236d240de85
Author: Iain Sandoe
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108259
--- Comment #3 from Iain Sandoe ---
this patch shows the problem - because it removes the shadowing "-L" options.
Obviously, we cannot apply it without creating 'regressions'...
[PATCH] modula-2, driver: Do not add extra '-L' options that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108242
Jakub Jelinek changed:
What|Removed |Added
Keywords|needs-bisection |
CC|
68 matches
Mail list logo
