This test helped discover PR116621, so it is worth being documented.
gcc/ChangeLog:
* doc/sourcebuild.texi: Document struct-layout-1.exp.
Signed-off-by: Dimitar Dimitrov
---
gcc/doc/sourcebuild.texi | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/
> > #include
> >
> > vint32m1_t foo(vint32m1_t vs1, vint32m1_t vs2, size_t vl)
> > {
> > return __riscv_vadd_vv_i32m1(vs1, vs2, vl);
> > }
>
> To double confirm, you mean "riscv64-linux-gnu-gcc-14 -march=rv64gcv
> -mabi=lp64d -flto -O0 tmp.c -c -S -o -" with above is able to reproduce this
On Sat, Sep 7, 2024 at 4:11 PM haochen.jiang wrote:
>
> On Linux/x86_64,
>
> 506417dbc8b1cbc1133a5322572cf94b671aadf6 is the first bad commit
> commit 506417dbc8b1cbc1133a5322572cf94b671aadf6
> Author: Andrew MacLeod
> Date: Fri Sep 6 11:42:14 2024 -0400
>
> Before running fast VRP, make su
This is a simple fix which adds the target supports requirement of int128
to the testcase too.
Pushed as obvious after testing to make sure the testcase is UNSUPPORTED now
with -m32 but working with -m64 on x86_64-linux-gnu.
gcc/testsuite/ChangeLog:
* gcc.dg/pr116588.c: Require int128.
On Linux/x86_64,
506417dbc8b1cbc1133a5322572cf94b671aadf6 is the first bad commit
commit 506417dbc8b1cbc1133a5322572cf94b671aadf6
Author: Andrew MacLeod
Date: Fri Sep 6 11:42:14 2024 -0400
Before running fast VRP, make sure all edges have EXECUTABLE set.
caused
FAIL: gcc.dg/pr116588.c (t
Tested x86_64-pc-linux-gnu, applying to trunk.
-- 8< --
We were silently accepting the pr65923.C specialization of std::swap with
the wrong exception specification; it should be declared noexcept. Let's
limit ignoring mismatch with system headers to extern "C" functions so we
get a diagnostic fo
v2 Patch:
* adds proper changelog text
* fixes typo in c.opt
Currently the behaviour of Wmissing-field-initializers is inconsistent
between C and C++. The C warning assumes that missing designated
initializers are deliberate, and does not warn. The C++ warning does warn
for missin
It was pointed out in
https://gcc.gnu.org/pipermail/gcc-patches/2024-September/662183.html,
that the wording with this print has too many words.
Fixed thusly.
Pushed as obvious after a build and test for x86_64-linux-gnu.
gcc/ChangeLog:
* gimple-ssa-split-paths.cc (is_feasible_trace): F
On Sat, Sep 7, 2024, 11:07 AM Georg-Johann Lay wrote:
> Am 07.09.24 um 19:51 schrieb H.J. Lu:
> > On Sat, Sep 7, 2024 at 10:49 AM Georg-Johann Lay wrote:
> >> Am 07.09.24 um 18:35 schrieb Jeff Law:
> >>> On 9/6/24 3:40 AM, Georg-Johann Lay wrote:
> The reason for PR116326 is that LRA and re
Am 07.09.24 um 19:51 schrieb H.J. Lu:
On Sat, Sep 7, 2024 at 10:49 AM Georg-Johann Lay wrote:
Am 07.09.24 um 18:35 schrieb Jeff Law:
On 9/6/24 3:40 AM, Georg-Johann Lay wrote:
The reason for PR116326 is that LRA and reload require different
ELIMINABLE_REGS for a multi-register frame pointer.
It appears when we run the fast VRP algorithm, I was neglecting to set
all the edges to executable before starting, so a little garbage was
sneaking in once in a while...
Fixed by calling the same routine regular VRP calls to do this.
Bootstraps on x86_64-pc-linux-gnu with no regressions. Pu
On Mon, Aug 26, 2024 at 1:59 PM Peter Frost wrote:
>
> Currently the behaviour of Wmissing-field-initializers is inconsistent
> between C and C++. The C warning assumes that missing designated
> initializers are deliberate, and does not warn. The C++ warning does warn
> for missing designated init
On Sat, Sep 7, 2024 at 10:49 AM Georg-Johann Lay wrote:
>
> Am 07.09.24 um 18:35 schrieb Jeff Law:
> > On 9/6/24 3:40 AM, Georg-Johann Lay wrote:
> >> The reason for PR116326 is that LRA and reload require different
> >> ELIMINABLE_REGS for a multi-register frame pointer. As ELIMINABLE_REGS
> >>
Am 07.09.24 um 18:35 schrieb Jeff Law:
On 9/6/24 3:40 AM, Georg-Johann Lay wrote:
The reason for PR116326 is that LRA and reload require different
ELIMINABLE_REGS for a multi-register frame pointer. As ELIMINABLE_REGS
is used to initialize static const objects, it is not possible to make
ELIMIN
On Sat, 07 Sep 2024 10:32:07 PDT (-0700), jeffreya...@gmail.com wrote:
On 8/25/24 8:03 PM, Jiawei wrote:
在 2024/8/25 23:38, Jeff Law 写道:
On 8/19/24 2:14 AM, shiyul...@iscas.ac.cn wrote:
From: yulong
This patch try to fix a bug[116347]. I change the name of the micro-
arch,
because I thi
Hi Iain,
>> This does fix the bootstrap problem on those, thanks
>> In this case, I’d like to test it across the OS versions I still test
>> regularly - but the machines are all going to be tied up testing the 11.5 RC
>> - so it might be a week or so. I do want to get this in as soon as poss -
ping**many on this patch, originally from January.
In latest round, Richard suggested that David should have the last say, I’ve
never had any response.
> Le 27 juin 2024 à 19:08, FX Coudert a écrit :
>
> Among the review comments from the last round, Jakub suggested:
>
>> Perhaps libgccjit.h
On 8/25/24 8:03 PM, Jiawei wrote:
在 2024/8/25 23:38, Jeff Law 写道:
On 8/19/24 2:14 AM, shiyul...@iscas.ac.cn wrote:
From: yulong
This patch try to fix a bug[116347]. I change the name of the micro-
arch,
because I think micro-arch and core have the same name that caused
the error.
gc
On 9/6/24 11:30 AM, Jin Ma wrote:
When we use flto, the function list of rvv will be generated twice,
once in the cc1 phase and once in the lto phase. However, due to
the different generation methods, the two lists are different.
For example, when there is no zvfh or zvfhmin in arch, it is
ge
On 9/6/24 5:32 AM, Jin Ma wrote:
In the process of DF to SI, we generally use "unsigned_fix" rather than
"truncate" for conversion. Although this has no effect in general,
unexpected ICE often occurs when precise semantic analysis is required.
gcc/ChangeLog:
* config/riscv/riscv.md:
On 9/5/24 9:09 PM, YunQiang Su wrote:
ChangeLog
* .gitignore: Add .vscode.
OK
jeff
On 9/5/24 11:07 PM, Zhao Dingyi wrote:
This patch aims to add the missing instruction types to the XiangShan-
Nanhu scheduler model.
The current XiangShan -Nanhu model lacks the trap, atomic trap,
fcvt_i2f, and fcvt_f2i instructions.
The trap, atomic, and i2f instructions belong to xs_jmp_r
On 9/6/24 3:40 AM, Georg-Johann Lay wrote:
The reason for PR116326 is that LRA and reload require different
ELIMINABLE_REGS for a multi-register frame pointer. As ELIMINABLE_REGS
is used to initialize static const objects, it is not possible to make
ELIMINABLE_REGS to depend on options or pat
On 9/6/24 11:40 AM, Jin Ma wrote:
Since the THeadVector vsetvli does not support vl as an immediate, we
need to convert 0 to zero when outputting asm.
PR target/116592
gcc/ChangeLog:
* config/riscv/thead.cc (th_asm_output_opcode): Change '0' to
"zero"
gcc/testsuite/ChangeLo
Am 06.09.24 um 20:58 schrieb Steve Kargl:
Your testcases are all free source form. In fixed
form, gfortran would need to deal with 'u = 1 2 3 4 u _8'
I don't have the patch in my tree at the moment,
it isn't clear to me if the matcher for an unsigned
constant is prepared to deal with space betwe
Am 06.09.24 um 20:15 schrieb Steve Kargl:
+Generally, unsigned integers are only permitted as data in intrinsics.
Does the word 'intrinsics' apply to 'intrinsic operators'
or 'intrinsic subprograms' or both? This might benefit from
a big of wordiness.
You're right, that wasn't clear at all.
Ping https://gcc.gnu.org/pipermail/gcc-patches/2024-August/661510.html
Tested on x86_64-darwin, powerpc64le-linux, OK for trunk?
--- 8< ---
As noted in the PR the action of the existing implementation was to
treat a false value from await_suspend () as equivalent to "do not
suspend". Actually it needs to be the equivalent of "resume" - and
we need to restart the d
> #include
>
> vint32m1_t foo(vint32m1_t vs1, vint32m1_t vs2, size_t vl)
> {
> return __riscv_vadd_vv_i32m1(vs1, vs2, vl);
> }
To double confirm, you mean "riscv64-linux-gnu-gcc-14 -march=rv64gcv
-mabi=lp64d -flto -O0 tmp.c -c -S -o -" with above is able to reproduce this
ICE?
Pan
-Or
> > +/* Test that we do not have ice when compile */
> > +
> > +/* { dg-do run } */
> > +/* { dg-options "-march=rv64gcv -mabi=lp64d -mrvv-vector-bits=zvl -flto
> > -O2 -fno-checking" } */
> > +
> > +#include
> > +
> > +int
> > +main ()
> > +{
> > + size_t vl = 8;
> > + vint32m1_t vs1 = {};
> >
On Sat, Sep 07, 2024 at 07:50:29AM +0200, Martin Uecker wrote:
> > 2. Apple's implementation supports expressions in the '__counted_by'
> > attribute, thus the 'count' may be an R-value that can't have its
> > address taken.
> >
> > [1]
> > https://discourse.llvm.org/t/rfc-introducing-new-clang
> Am 06.09.2024 um 20:50 schrieb Jakub Jelinek :
>
> Hi!
>
> cat abc.C
> #define A(n) struct T##n {} t##n;
> #define B(n) A(n##0) A(n##1) A(n##2) A(n##3) A(n##4) A(n##5) A(n##6) A(n##7)
> A(n##8) A(n##9)
> #define C(n) B(n##0) B(n##1) B(n##2) B(n##3) B(n##4) B(n##5) B(n##6) B(n##7)
> B(n##8
32 matches
Mail list logo
