https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113373
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113373
--- Comment #8 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:86f3cbdaa6f60eaff1cdb4ab2f1a9bc796b67207
commit r14-8330-g86f3cbdaa6f60eaff1cdb4ab2f1a9bc796b67207
Author: Richard Biener
Date:
On Fri, Jan 19, 2024 at 5:06 PM Georg-Johann Lay wrote:
>
>
>
> Am 18.01.24 um 20:54 schrieb Roger Sayle:
> >
> > This patch tweaks RTL expansion of multi-word shifts and rotates to use
> > PLUS rather than IOR for disjunctive operations. During expansion of
> > these operations, the middle-end
OK I guess change register_operand into REG_P should fix those ICEs.
I will have a try and send a patch.
Thanks.
juzhe.zh...@rivai.ai
From: Andrew Pinski
Date: 2024-01-22 15:14
To: juzhe.zh...@rivai.ai
CC: gcc-patches; Kito.cheng; kito.cheng; jeffreyalaw; vineetg; Robin Dapp;
palmer;
On Fri, Jan 19, 2024 at 9:08 PM Tobias Burnus wrote:
>
> This patch fixes PR111966, i.e. when compiling offloaded code with "-g"
> but without "-march=", mkoffload created a file with e_flags set to
> gfx803/fiji as architecture - while all other files used gfx900, which
> the linker did not
On Fri, Jan 19, 2024 at 5:26 PM Qing Zhao wrote:
>
>
>
> > On Jan 19, 2024, at 4:30 AM, Richard Biener
> > wrote:
> >
> > On Thu, Jan 18, 2024 at 3:46 PM Qing Zhao wrote:
> >>
> >>
> >>
> >>> On Jan 17, 2024, at 1:43 AM, Richard Biener
> >>> wrote:
> >>>
> >>> On Wed, Jan 17, 2024 at 7:42 AM
On Sun, Jan 21, 2024 at 2:33 PM Hans-Peter Nilsson wrote:
>
> Tested x86_64-linux-gnu. Ok to commit?
>
> Or, does the message need more tweaking?
> (If so, suggestions from native speakers?)
> FWIW, I found no PR for just the message being bad.
>
> -- >8 --
> When you're not regularly exposed to
在 2024/1/19 下午4:51, chenglulu 写道:
在 2024/1/19 下午1:46, Xi Ruoyao 写道:
On Wed, 2024-01-17 at 17:57 +0800, chenglulu wrote:
Virtual register 1479 will be used in insn 2744, but register 1479
was
assigned the REG_UNUSED attribute in the previous instruction.
The attached file is the wrong
On Sun, Jan 21, 2024 at 11:06 PM juzhe.zh...@rivai.ai
wrote:
>
> Hi, this patch causes these regressions (all ICEs) in RISC-V backend:
Note this is related to the fix for PR 109092.
But right now register_operand still accepts `(SUBREG (MEM...))`
before reload ...
So basically there is a check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113420
JuzheZhong changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
Hi, this patch causes these regressions (all ICEs) in RISC-V backend:
FAIL: gcc.dg/torture/float32-tg-2.c -O1 (internal compiler error: in
reg_or_subregno, at jump.cc:1895)
FAIL: gcc.dg/torture/float32-tg-2.c -O1 (test for excess errors)
FAIL: gcc.dg/torture/float32-tg-2.c -O2 (internal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113530
--- Comment #6 from Matthias Klose ---
> Does the GCC 13 branch actually try to build libgo for arc-linux-gnu?
I don't know. I usually configure with --enable-languages=go, which I didn't
with 13, but by a mistake did with 14. So maybe just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113537
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
Committed, thanks
xu...@eswincomputing.com
From: juzhe.zh...@rivai.ai
Date: 2024-01-22 14:40
To: Li Xu; gcc-patches
CC: kito.cheng; palmer; Li Xu
Subject: Re: [PATCH v2] RISC-V: Bugfix for resolve_overloaded_builtin[PR113420]
LGTM.
juzhe.zh...@rivai.ai
From: Li Xu
Date: 2024-01-22 12:11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113420
--- Comment #1 from GCC Commits ---
The master branch has been updated by Li Xu :
https://gcc.gnu.org/g:46a664dd59ec6c1121914d6857d6edb94501c517
commit r14-8328-g46a664dd59ec6c1121914d6857d6edb94501c517
Author: xuli
Date: Mon Jan 22
Notice there is a AI benchmark, GCC vs Clang has 3% performance drop.
It's because Clang/LLVM has a simplification transform vmv.v.x (avl = 1) into
vmv.s.x.
Since vmv.s.x has more flexible vsetvl demand than vmv.v.x that can allow us to
have
better chances to fuse vsetvl.
Consider this
LGTM.
juzhe.zh...@rivai.ai
From: Li Xu
Date: 2024-01-22 12:11
To: gcc-patches
CC: kito.cheng; palmer; juzhe.zhong; xuli
Subject: [PATCH v2] RISC-V: Bugfix for resolve_overloaded_builtin[PR113420]
From: xuli
v2:
Avoid internal ICE for the case below.
vint8mf8_t test_vle8_v_i8mf8_m(vbool64_t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113537
--- Comment #2 from Andrew Pinski ---
aarch64_vectorize_vec_perm_const does not handle at all the case where the 2
modes are different.
Thanks, nice result, I'll try to run the performance benchmarks that are
coming with libstdc++ to see if they spot anything.
That's tests in testsuite/performance folder in case you want to have a
try yourself.
François
On 18/01/2024 10:26, Huanghui Nie wrote:
Yes, I have. I did a
Since the match.pd transforms (zero_one == 0) ? y : z y,
into ((typeof(y))zero_one * z) y. Add splitters to recongize
this expression to generate SFB instructions.
gcc/ChangeLog:
PR target/113095
* config/riscv/sfb.md: New splitters to rewrite single bit
sign extension
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113537
--- Comment #1 from Andrew Pinski ---
One gimple level thing I noticed is we produce:
```
_1 = VEC_PERM_EXPR ;
_3 = BIT_FIELD_REF <_1, 64, 0>;
```
But Maybe that should just be:
```
_3 = VEC_PERM_EXPR ;
```
Which is what the vector might
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113537
Bug ID: 113537
Summary: ext should be used more for __builtin_shufflevector
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113536
Bug ID: 113536
Summary: valid reduction expression rejected by -gnatVo
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90463
--- Comment #2 from sandra at gcc dot gnu.org ---
A quick look through the lists of -Wall and -Wextra options turned up some
others that are missing, too. I'm trying to do a more thorough patch.
a:z@
From: xuli
v2:
Avoid internal ICE for the case below.
vint8mf8_t test_vle8_v_i8mf8_m(vbool64_t vm, const int32_t *rs1, size_t vl) {
return __riscv_vle8(vm, rs1, vl);
}
v1:
Change the hash value of overloaded intrinsic from considering
all parameter types to:
1. Encoding vector data type
2. In
On Sat, Jan 20, 2024 at 10:30 PM H.J. Lu wrote:
>
> When an interrupt handler is implemented by an assembly stub which does:
>
> 1. Save all registers.
> 2. Call a C function.
> 3. Restore all registers.
> 4. Return from interrupt.
>
> it is completely unnecessary to save and restore any
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113530
--- Comment #5 from Ian Lance Taylor ---
Does the GCC 13 branch actually try to build libgo for arc-linux-gnu?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113507
Kewen Lin changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109705
Kewen Lin changed:
What|Removed |Added
CC||linkw at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113535
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2024-01-22
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113535
Bug ID: 113535
Summary: rs6000, testsuite: Re-visit the current vect_* for
Power
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113533
--- Comment #5 from Oleg Endo ---
(In reply to Andrew Pinski from comment #3)
> That seems to make the cost of a load/store if just an index, the same as the
> cost
> as the index. Which definitely seems wrong. It should be the cost of the
>
LGTM :)
On Mon, Jan 22, 2024 at 10:49 AM Juzhe-Zhong wrote:
>
> vfirst/vmsbf/vmsif/vmsof instructions are supposed to demand ratio instead of
> demanding sew_lmul.
> But my previous typo makes VSETVL PASS miss honor the risc-v v spec.
>
> Consider this following simple case:
>
> int foo4 (void
vfirst/vmsbf/vmsif/vmsof instructions are supposed to demand ratio instead of
demanding sew_lmul.
But my previous typo makes VSETVL PASS miss honor the risc-v v spec.
Consider this following simple case:
int foo4 (void * in, void * out)
{
vint32m1_t v = __riscv_vle32_v_i32m1 (in, 4);
v =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113534
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113533
--- Comment #4 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #3)
> The way aarch64 implements its _rtx_costs is that it cases SET and if the
> LHS is a mem, then it is the cost of the store there and returns true
> (though you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113533
--- Comment #3 from Andrew Pinski ---
(In reply to Oleg Endo from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > This is most likely a cost model issue on sh3.
>
> You mean this one (sh.cc, sh_rtx_costs)?
>
> /* The cost of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113534
Bug ID: 113534
Summary: printf might report segmentation fault under -mabi=ms
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113382
--- Comment #3 from John David Anglin ---
btf_kflag is set here:
else if (btf_kind == BTF_KIND_ENUM)
{
btf_kflag = dtd->dtd_enum_unsigned
? BTF_KF_ENUM_UNSIGNED
: BTF_KF_ENUM_SIGNED;
(gdb) p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113533
--- Comment #2 from Oleg Endo ---
(In reply to Andrew Pinski from comment #1)
> This is most likely a cost model issue on sh3.
You mean this one (sh.cc, sh_rtx_costs)?
/* The cost of a mem access is mainly the cost of the address mode.
Hi all,
Recently, I happened to run i386.exp under -DDEBUG and found some fail.
This patch aims to fix that. Ok for trunk?
Thx,
Haochen
gcc/testsuite/ChangeLog:
* gcc.target/i386/adx-check.h: Include stdio.h when DEBUG
is defined.
*
On Sun, 2024-01-21 at 19:14 -0700, Jeff Law wrote:
> The change for pr111267 twiddled code generation for sh/pr59533-1.c
>
> We end up eliminating two comparisons, but require two shll instructions
> to do so. And in a couple places we're using an addc sequence rather
> than a subc sequence.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113533
Andrew Pinski changed:
What|Removed |Added
Target||sh3-linux-gnu
Target Milestone|---
On 1/15/24 06:34, Richard Biener wrote:
When the x86 backend generates code for cpymem with the rep_8byte
strathegy for the 8 byte aligned main rep movq it needs to compute
an adjusted pointer to the source after doing a prologue aligning
the destination. It computes that via
src_ptr +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113533
Bug ID: 113533
Summary: [14 Regression] Code generation regression after
change for pr111267
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
The change for pr111267 twiddled code generation for sh/pr59533-1.c
We end up eliminating two comparisons, but require two shll instructions
to do so. And in a couple places we're using an addc sequence rather
than a subc sequence. This patch adjusts the expected codegen for the
test as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
--- Comment #14 from Lipeng Zhu ---
(In reply to Lipeng Zhu from comment #13)
> OK, I think I find the root cause of this error, when thread number greater
> than 1000, the file_name = 1000_tst.dat, character(11) will overflow. This
> will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #15 from kargl at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #14)
> On Sun, Jan 21, 2024 at 09:52:39PM +, anlauf at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
> >
> > I think
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
--- Comment #14 from Steve Kargl ---
On Sun, Jan 21, 2024 at 09:52:39PM +, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
>
> I think that you cannot do
>
> + if (MPFR_HALF_CYCLE)
>
> you really
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113401
--- Comment #3 from Iain Sandoe ---
for platforms using pthreads as the underlying resource, then perhaps we can do
this without thread_atexit (which I do not see in many places) by using
pthread_cleanup_push ()
not sure if gthr.h abstracts
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113403
--- Comment #14 from Iain Sandoe ---
Created attachment 57182
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57182=edit
patch under test
this is what I'm testing
- these functions are removed from libgcc.a and added to libgcc_eh.a
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91681
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
On Jan 21 2024, Jeff Law wrote:
> Yea. The biggest problem with ATTRIBUTE_UNUSED is that it's a "may be
> unused" and thus if the code changes it's sometimes left on an parameter
> incorrectly. C++ allows us to specify a "is definitely unused" concept by
> dropping the parameter's name, but
On 1/16/24 10:13, Mary Bennett wrote:
gcc/testsuite/ChangeLog:
* gcc.target/riscv/cv-alu-fail-compile.c: Change warning to error.
AFAICT this is independent of the other patches and fixes a clear
testsuite issue. I've pushed it to the trunk.
Thanks,
Jeff
On 1/16/24 09:25, Mary Bennett wrote:
Spec:
github.com/openhwgroup/core-v-sw/blob/master/specifications/corev-builtin-spec.md
Contributors:
Mary Bennett
Nandni Jamnadas
Pietra Ferreira
Charlie Keaney
Jessica Mills
Craig Blackmore
Simon Cook
Jeremy Bennett
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82420
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111279
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
On 1/16/24 09:55, Mikael Pettersson wrote:
On Thu, 4 Jan 2024 14:39:23 -0700, Jeff Law wrote:
On 1/4/24 02:23, Mikael Pettersson wrote:
emit_library_call_value_1 calls emit_push_insn with NULL_TREE
for TYPE. Sometimes emit_push_insn needs to assign a temp with
that TYPE, which causes a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82420
--- Comment #7 from GCC Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:bdcf7226c9fe87352466eb9a6bfc58fa24b3e5e1
commit r14-8324-gbdcf7226c9fe87352466eb9a6bfc58fa24b3e5e1
Author: Mikael Pettersson
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111279
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:bdcf7226c9fe87352466eb9a6bfc58fa24b3e5e1
commit r14-8324-gbdcf7226c9fe87352466eb9a6bfc58fa24b3e5e1
Author: Mikael Pettersson
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113382
--- Comment #2 from John David Anglin ---
We have:
.word 0x8604 ; btt_info: kind=6, kflag=1, vlen=4
This seems correct encoding:
/* Encoding for struct btf_type.info. */
#define BTF_TYPE_INFO(kind, kflag, vlen) \
On 1/17/24 11:21, Martin Jambor wrote:
Hi,
PR 110422 shows that SRA can ICE assuming there is a single edge
outgoing from a block terminated with an asm goto. We need that for
BB-terminating statements so that any adjustments they make to the
aggregates can be copied over to their
On 1/19/24 18:18, 钟居哲 wrote:
OK. I saw the other arguments there:
tree fntype ATTRIBUTE_UNUSED,
rtx libname ATTRIBUTE_UNUSED,
So I leverage these and add ATTRIBUTE_UNUSED to 'fndecl'
Maybe it's better remove all arguments for
The signature was still using ATTRIBUTE_UNUSED and actually marked one
of the used arguments with ATTRIBUTE_UNUSED.
This patch drops the decorations and instead remove the name of
arguments which are actually unused which is the preferred way to handle
this now when we can.
Bootstrapped.
Snapshot gcc-14-20240121 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20240121/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #10 from Jonathan Wakely ---
Fixed on trunk so far.
Tested aarch64-linux. Pushed to trunk.
Backport to gcc-13 would be good too, I think.
-- >8 --
Currently trying to use std::format with certain specializations of
std::chrono::time_point is ill-formed, due to one member function of the
__formatter_chrono type which tries to write a time_point
Tested aarch64-linux. Pushed to trunk. Backport needed to gcc-13 too.
-- >8 --
THe std::chrono::file_clock conversions were not using common_type and
so failed to compile when converting anything that should have increased
precision after arithmetic with a std::chrono::seconds value.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113500
--- Comment #9 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:7431fcea6b72beb54abb1932c254ac0e76bd0bde
commit r14-8321-g7431fcea6b72beb54abb1932c254ac0e76bd0bde
Author: Jonathan Wakely
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
Bug 87403 depends on bug 113532, which changed state.
Bug 113532 Summary: Warn about definition of macros that shadow keywords
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113532
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113532
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109994
--- Comment #4 from Jonathan Wakely ---
*** Bug 113532 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113532
Bug ID: 113532
Summary: Warn about definition of macros that shadow keywords
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Keywords: diagnostic
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113458
--- Comment #11 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #9)
> (In reply to Andrew Pinski from comment #8)
> > (In reply to Andrew Pinski from comment #7)
> > > But the load is still using inserts and tbl. I have not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113382
--- Comment #1 from John David Anglin ---
Similar fails:
FAIL: gcc.dg/debug/btf/btf-enum-1.c scan-assembler-times [\\t ]0x604[\\t
]+[^\\n]*btt_info 1
FAIL: gcc.dg/debug/btf/btf-enum-small.c scan-assembler-times [\\t
]0x602[\\t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113152
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2024-01-21
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112293
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111267
--- Comment #11 from GCC Commits ---
The master branch has been updated by Roger Sayle :
https://gcc.gnu.org/g:86de9b66480b710202a2898cf513db105d8c432f
commit r14-8319-g86de9b66480b710202a2898cf513db105d8c432f
Author: Roger Sayle
Date: Sun
Am 20.01.24 um 23:42 schrieb Alexander Westbrooks:
Based on what I am reading here, I can either do the DCO path or the copy
right form path? Or is it both, where I send in the copy right forms and
then on every commit I put the DCO?
I thought the text is pretty clear. As already mentioned,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89180
Bug 89180 depends on bug 90464, which changed state.
Bug 90464 Summary: Documentation: incorrect description of -Wunused
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90464
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90464
sandra at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
gcc/ChangeLog
PR c++/90464
* doc/invoke.texi (Warning Options): Document that -Wunused-parameter
isn't enabled by -Wunused unless -Wextra is provided, and that
-Wunused does enable -Wunused-const-variable=1 for C. Clarify that
-Wunused doesn't enable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90464
--- Comment #1 from GCC Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:5c3e2e134ba8e692f317f21aea10b70bfe14cfc1
commit r14-8318-g5c3e2e134ba8e692f317f21aea10b70bfe14cfc1
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113531
Bug ID: 113531
Summary: AddressSanitizer: stack-use-after-scope when iterating
over initializer list
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112293
--- Comment #8 from Jonathan Wakely ---
And here too: https://bugzilla.redhat.com/show_bug.cgi?id=2259394
Hi Mikael!
Am 21.01.24 um 11:50 schrieb Mikael Morin:
Hello,
Le 20/01/2024 à 22:58, Harald Anlauf a écrit :
Dear all,
here's the first part of an attempt to fix issues with optional
dummy arguments as actual arguments to optional dummies. This patch
rectifies the case of scalar dummies with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113377
--- Comment #9 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:68862e5c75ef0e875e690f0880a96fc6200d1682
commit r14-8317-g68862e5c75ef0e875e690f0880a96fc6200d1682
Author: Harald Anlauf
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113492
--- Comment #12 from GCC Commits ---
The master branch has been updated by Martin Uecker :
https://gcc.gnu.org/g:1ead42f9836a13cbbe6a2be685f76750583ae320
commit r14-8316-g1ead42f9836a13cbbe6a2be685f76750583ae320
Author: Martin Uecker
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113530
--- Comment #4 from John David Anglin ---
Created attachment 57181
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57181=edit
Add defines for hppa and hppa64 to goarch.sh
Untested.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360
--- Comment #8 from Walter Spector ---
Hi,
It is a good point. The message is helpful when issued within a procedure.
At module scope, it doesn't mean much since everything at that level is SAVE
anyway. This is similar to what happens in C:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57360
--- Comment #7 from kargl at gcc dot gnu.org ---
Upon some additional thinking, I wonder how useful this will be compared
to the possible volume of warning messages from modern Fortran. Consider
this code:
module foo
integer :: j = 2
type
On Thu, Jan 18, 2024 at 3:37 PM Tom Tromey wrote:
>
> Andrew> This change is causing some problems for me.
>
> Yeah, Tom de Vries as well.
>
> Andrew> One of my build machines has 2 versions of guile installed. One is
> Andrew> guile 2.0.14 and the other is guile 2.2.21.
>
> Andrew> When GDB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113530
--- Comment #3 from John David Anglin ---
Looks like a Makefile issue:
echo " _BigEndian = `$(SHELL) $(srcdir)/goarch.sh $(GOARCH)
bigendian`" >> zgoarch.go.tmp
At this time, hppa doesn't support go.
#11 from Matthias Klose ---
seen with trunk 20240121 on m68k-linux-gnu, trying to build libgo:
go1: internal compiler error: in set_from, at go/gofrontend/types.cc:2863
0x67b949 Ptrmask::set_from(Gogo*, Type*, long, long)
../../src/gcc/go/gofrontend/types.cc:2863
0x9681a8 Ptrmask::set_from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113530
Matthias Klose changed:
What|Removed |Added
CC||danglin at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113336
Hans-Peter Nilsson changed:
What|Removed |Added
CC||hp at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113530
--- Comment #1 from Matthias Klose ---
sorry, arc-linux-gnu
Assignee: ian at airs dot com
Reporter: doko at gcc dot gnu.org
Target Milestone: ---
seen with trunk 20240121 on arch-linux-gnu, works with the gcc-13 branch,
building a gccgo cross compiler targeting arc-linux-gnu:
[...]
libtool: compile:
/home/packages/cross/14/p/gcc
Hello All:
New pass to replace adjacent memory addresses lxv with lxvp.
Added common infrastructure for load store fusion for
different targets.
Common routines are refactored in fusion-common.h.
AARCH64 load/store fusion pass is not changed with the
common infrastructure.
For AARCH64
1 - 100 of 114 matches
Mail list logo
