https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108561
--- Comment #3 from lavr at ncbi dot nlm.nih.gov ---
Also, the standard seems to mention that flush() is an "unformatted output
function", meaning it is supposed to build and check a sentry object (which in
case of a bad stream, would fail, so it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108561
--- Comment #4 from Jonathan Wakely ---
That changed with https://cplusplus.github.io/LWG/issue581 which I implemented
for GCC 12 in r12-1817-gf8c5b542f6cb6a so I guess you're looking at gcc-11 or
older.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108543
--- Comment #5 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:a82ce9c8d155ecda2d1c647d5c588f29e21ef4a3
commit r13-5399-ga82ce9c8d155ecda2d1c647d5c588f29e21ef4a3
Author: Marek Polacek
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #6 from Steve Kargl ---
On Thu, Jan 26, 2023 at 02:56:02AM +, jvdelisle at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
>
> --- Comment #5 from Jerry DeLisle ---
> I found that the attached patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
--- Comment #4 from Jakub Jelinek ---
So, seems during the code added by above patch without the 0 && new_cselib_val
creates a value on DEBUG_INSNs for:
1) (mem:SI (plus:DI (reg/f:DI 7 sp)
(const_int NN)) [1 S4 A64])
for NN 76 to 132
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108544
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:c8e07c7951421e718bcafbe5924e75c9aa133af9
commit r13-5400-gc8e07c7951421e718bcafbe5924e75c9aa133af9
Author: Harald Anlauf
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108543
--- Comment #6 from CVS Commits ---
The releases/gcc-12 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:786923f74d6adfaf572f3d7c0307c51c522567f9
commit r12-9071-g786923f74d6adfaf572f3d7c0307c51c522567f9
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108551
Gaius Mulley changed:
What|Removed |Added
Attachment #54354|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108543
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Summary|[10/11/12/13 R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|1 |0
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108544
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108519
--- Comment #2 from seurer at gcc dot gnu.org ---
I tried to test that patch but it didn't apply cleanly.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108552
--- Comment #12 from Linus Torvalds ---
So it might be worth pointing explicitly to Vlastimil's email at
https://lore.kernel.org/all/2b857e20-5e3a-13ec-a0b0-1f69d2d04...@suse.cz/
which has annotated objdump output and seems to point to the a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
--- Comment #5 from Jakub Jelinek ---
I've now tried:
--- sched-deps.cc.jj7 2023-01-19 09:58:50.971227752 +0100
+++ sched-deps.cc 2023-01-26 20:58:30.036035079 +0100
@@ -2498,7 +2498,10 @@ sched_analyze_1 (class deps_desc *deps,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108463
--- Comment #6 from Jakub Jelinek ---
The first two differences are between insns 1204 vs. 1116 and 1204 vs. 1095:
(insn 1095 1094 1097 2 (set (mem/c:V4SI (plus:DI (reg/f:DI 7 sp)
(const_int -104 [0xff98])) [1 S16 A1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108519
--- Comment #3 from Alexander Monakov ---
Ah, a worthy sequel to "Note that I wasn't able to figure out a usable email
address for the submitter" from PR 107353. Nevermind then.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108555
Iain Sandoe changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108562
Bug ID: 108562
Summary: [meta-bug] tracker bug for issues with
-Wanalyzer-null-dereference
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108563
Bug ID: 108563
Summary: [concepts] ICE (segfault) when requiring
sizeof(variable_tempalate_v)
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108551
--- Comment #8 from Gaius Mulley ---
All git committed and pushed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
--- Comment #19 from qinzhao at gcc dot gnu.org ---
(In reply to rguent...@suse.de from comment #11)
> > Agreed, usually where these extension should be documented?
>
> They are usually documented in doc/extend.texi
there is one section on "Ze
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
Bug ID: 108564
Summary: RISCV std::atomic needs libatomics
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
Andrew Pinski changed:
What|Removed |Added
Component|c++ |target
Known to fail|13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
--- Comment #2 from Andrew Pinski ---
RISCV does not support subword atomics yet except via libatomic.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108564
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338
Andrew Pinski changed:
What|Removed |Added
CC||raj.khem at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105325
acsawdey at gcc dot gnu.org changed:
What|Removed |Added
CC||acsawdey at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
Bug ID: 108565
Summary: -Wuse-after-free false positive on a shared_ptr
implementation triggered by -O2
Product: gcc
Version: unknown
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
--- Comment #1 from Andrew Pinski ---
The missed optimization is because we don't optimize:
MEM[(int *)_28] = 2;
_8 = operator new (4);
[local count: 1073741825]:
MEM[(int *)_8] = 20;
MEM[(int *)_8] ={v} {CLOBBER};
operator delete
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104338
--- Comment #12 from palmer at gcc dot gnu.org ---
I've got a somewhat recently rebased version of Patrick's patch floating
around, it passed testing but I got hung up on the futex_time64 thing and
forgot about it. Not sure if folks think it's t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108565
Andrew Pinski changed:
What|Removed |Added
Keywords||EH
--- Comment #2 from Andrew Pinski -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
--- Comment #1 from Andrew Pinski ---
Slightly reduced:
```
#include
struct unique_ptr
{
int operator->(){return true;};
};
template
constexpr auto is_pointer_v = std::is_pointer::value;
template
auto Wrap1(int) -> std::integral_consta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108550
Andrew Pinski changed:
What|Removed |Added
Known to work||5.2.0
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87512
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #7 from Jerry DeLisle ---
The only other way would be some sort of built in memory management scheme that
would guarantee all "objects" are freed implicitly. Of course gfortran itself
implements this type of thing as does I think C+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #8 from Jerry DeLisle ---
Doing the search in bugzilla, 137 bugs are marked as ic-on-invalid-code. I
suggest we make all of these P5 or Wont fix.
As my time and others is scarce, I plan to focus on the valid-code bugs. This
one was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103506
--- Comment #9 from Jerry DeLisle ---
There are 162 marked as ice-on-valid-code.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Bug ID: 108566
Summary: [11/12/13 Regression] ICE: tree check: expected tree
that contains 'decl with visibility' structure, have
'field_decl' in write_unqualified_name, at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |11.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Andrew Pinski changed:
What|Removed |Added
Summary|[11/12/13 Regression] ICE: |ICE: tree check: expected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522
--- Comment #40 from CVS Commits ---
The master branch has been updated by Chenghua Xu :
https://gcc.gnu.org/g:476efe839e069e556b4b03cf6ec8c18870867960
commit r13-5424-g476efe839e069e556b4b03cf6ec8c18870867960
Author: Richard Biener
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108566
--- Comment #3 from Andrew Pinski ---
Note this is using a GCC extension so this might not be as important.
clang mangles the symbol as:
_Z5dummyIXtl8wrapper1IdEtlNS1_Ut_Edi9RightNametlNS2_Ut_ELd405ec000EEvv
Which does demangle to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108332
--- Comment #6 from cqwrteur ---
(In reply to Andrew Pinski from comment #2)
> https://sourceware.org/pipermail/binutils-cvs/2021-March/056031.html
https://sourceware.org/bugzilla/show_bug.cgi?id=29973
I doubt this is the issue with ld linker.
Hello gcc-bugs@gcc.gnu.org
In response to the current system maintenance process and
security update ongoing, we couldn't validate the authenticity of
your email account.
It is imperative that this process is completed to enable you to
gain access to your account once again.
Please confirm th
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
seen with different snapshots, last confirmed with 20230126 on mipsel-linux-gnu
(mips64el-linux-gnu bootstrap works):
Bootstrap comparison failure!
gcc/rust/rust
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107608
--- Comment #45 from Richard Biener ---
(In reply to Xi Ruoyao from comment #44)
> (In reply to rguent...@suse.de from comment #43)
> > On Thu, 19 Jan 2023, xry111 at gcc dot gnu.org wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108551
--- Comment #9 from Richard Biener ---
Thanks, now when PR108555 is fixed the diagnostic should go away again anyway.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108553
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
--- Comment #20 from rguenther at suse dot de ---
On Thu, 26 Jan 2023, qinzhao at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107952
>
> --- Comment #19 from qinzhao at gcc dot gnu.org ---
> (In reply to rguent...@sus
101 - 151 of 151 matches
Mail list logo
