https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113607
--- Comment #4 from Robin Dapp ---
I cannot reproduce it either, tried with -ftree-vectorize as well as
-fno-vect-cost-model.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113609
--- Comment #2 from Uroš Bizjak ---
(In reply to Hongtao Liu from comment #1)
> Since they're different modes, CCZ for cmp, but CCS for kortest, it could be
> diffcult to optimize it in RA stage by adding alternatives(like we did for
> compared
It's fixed by this commit:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=d40b3c1e439db05c835b6bd4fd5bba58fda71dd6
juzhe.zh...@rivai.ai
From: Edwin Lu
Date: 2024-01-17 09:45
To: juzhe.zh...@rivai.ai; gcc-patches
CC: Patrick O'Neill
Subject: Re: [Committed V2] RISC-V: Fix regression (GCC-14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113600
--- Comment #3 from Richard Biener ---
I'll note that esp. two-lane reductions (or in general two-lane BB
vectorization) is hardly profitable on modern x86 uarchs unless the vectorized
code is interleaved with other non-vectorized code that can
gcc/ChangeLog:
* config/loongarch/loongarch.cc (loongarch_load_tls):
Load all types of tls symbols through one function.
(loongarch_got_load_tls_gd): Delete.
(loongarch_got_load_tls_ld): Delete.
(loongarch_got_load_tls_ie): Delete.
gcc/ChangeLog:
* config/loongarch/loongarch-protos.h (loongarch_symbol_extreme_p):
Add function declaration.
* config/loongarch/loongarch.cc (loongarch_symbolic_constant_p):
For SYMBOL_PCREL64, non-zero addend of "la.local $rd,$rt,sym+addend"
is not allowed
gcc/ChangeLog:
* config/loongarch/loongarch.cc (loongarch_call_tls_get_addr):
Add support for call36.
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/explicit-relocs-medium-call36-auto-tls-ld-gd.c:
New test.
---
gcc/config/loongarch/loongarch.cc | 20
Binutils does not support relaxation using four instructions to obtain
symbol addresses
gcc/ChangeLog:
* config/loongarch/loongarch.cc (loongarch_explicit_relocs_p):
When the code model of the symbol is extreme and -mexplicit-relocs=auto,
the macro instruction loading
v3 -> v4:
1. Add macro support for TLS symbols
2. Added support for loading __get_tls_addr symbol address using call36.
3. Merge template got_load_tls_{ld/gd/le/ie}.
4. Enable explicit reloc for extreme TLS GD/LD with -mexplicit-relocs=auto.
v2 -> v3:
1. Modify the detection rules of a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109705
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109705
--- Comment #15 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:bfd6b36f08021f023e0e9223f5aea315b74a5c56
commit r14-8443-gbfd6b36f08021f023e0e9223f5aea315b74a5c56
Author: Andrew Pinski
Date:
On Fri, Jan 26, 2024 at 7:23 AM chenxiaolong wrote:
>
> gcc/testsuite/ChangeLog:
OK
> * gcc.dg/signbit-2.c: Added additional "-mlsx" compilation options.
> * gfortran.dg/graphite/vect-pr40979.f90: Dito.
> * gfortran.dg/vect/fast-math-mgrid-resid.f: Dito.
> ---
>
On Fri, Jan 26, 2024 at 6:01 AM Andrew Pinski wrote:
>
> The 2 loops in octfapg_universe can and will be vectorized now
> after r14-333-g6d4b59a9356ac4 on targets that support multiplication
> in the long type. But the testcase does not check vect_long_mult for
> that, so this patch corrects that
On Fri, Jan 26, 2024 at 12:04 AM Tobias Burnus wrote:
>
> When targeting AMD GPUs, the LLVM assembler (and linker) are used.
>
> Two days ago LLVM changed the default for the AMDHSA code object
> version (COV) from 4 to 5.
>
> In principle, we do not care which COV is used as long as it works;
>
This patch causes the following regression:
FAIL: gcc.target/riscv/rvv/vsetvl/pr113429.c -O0 (test for excess errors)
FAIL: gcc.target/riscv/rvv/vsetvl/pr113429.c -O1 (test for excess errors)
FAIL: gcc.target/riscv/rvv/vsetvl/pr113429.c -O2 (test for excess errors)
FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113469
Li Pan changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105479
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-01-26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104427
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-8419-20240125172014-gc6c2a1d79eb-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240125 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102252
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.0
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90155
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-01-26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113469
--- Comment #1 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:d40b3c1e439db05c835b6bd4fd5bba58fda71dd6
commit r14-8442-gd40b3c1e439db05c835b6bd4fd5bba58fda71dd6
Author: Juzhe-Zhong
Date: Fri Jan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113612
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113612
Andrew Pinski changed:
What|Removed |Added
Keywords||error-recovery
Target Milestone|---
This patch fixes the recent noticed bug in RV32 glibc.
We incorrectly deleted a vsetvl:
...
and a4,a4,a3
vmv.v.i v1,0 ---> Missed vsetvl cause illegal
instruction report.
vse8.v v1,0(a5)
The root cause the laterin in LCM is incorrect.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113613
--- Comment #2 from Andrew Pinski ---
Note I don't know if this shows up in real programs but it might point to
something missing that might happen in real programs.
Another testcase this time without vectors:
```
double a[4];
double b[4];
gcc/testsuite/ChangeLog:
* gcc.dg/signbit-2.c: Added additional "-mlsx" compilation options.
* gfortran.dg/graphite/vect-pr40979.f90: Dito.
* gfortran.dg/vect/fast-math-mgrid-resid.f: Dito.
---
gcc/testsuite/gcc.dg/signbit-2.c | 1 +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113613
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
--- Comment #1 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113613
Bug ID: 113613
Summary: [14 Regression] Missing ldp/stp optimization sometimes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity:
-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-8419-20240125172014-gc6c2a1d79eb-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240125 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95960
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84114
Andrew Pinski changed:
What|Removed |Added
Known to work||12.1.0
--- Comment #12 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #22 from Hongtao Liu ---
typedef unsigned long mp_limb_t;
typedef long mp_size_t;
typedef unsigned long mp_bitcnt_t;
typedef mp_limb_t *mp_ptr;
typedef const mp_limb_t *mp_srcptr;
#define GMP_LIMB_BITS (sizeof(mp_limb_t) * 8)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89628
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #25 from john.harper at vuw dot ac.nz ---
With that program Intel's two compilers (ifort and ifx) both print
>.30D+01<
>.30E+01<
If your program removes the d0.2 stuff and changes e0.2 to es0.2e0, i.e.
character(20) :: fmt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113220
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2024-01-03 00:00:00 |2024-1-25
--- Comment #2 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113084
Andrew Pinski changed:
What|Removed |Added
Component|middle-end |target
--- Comment #3 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109705
Andrew Pinski changed:
What|Removed |Added
Keywords||patch
URL|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100212
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 100212, which changed state.
Bug 100212 Summary: UB (shift by -1) in aarch64_classify_index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100212
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100212
--- Comment #3 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:0c2583dc2575f3f64e3d09e12c296eb56f01916d
commit r14-8441-g0c2583dc2575f3f64e3d09e12c296eb56f01916d
Author: Andrew Pinski
Date:
The problem here is we don't check the return value of exact_log2
and always use that result as shifter. This fixes the issue by avoiding
the shift if the value was `-1` (which means the value was not exact a power of
2);
in this case we could either check if the values was equal to -1 or not
The 2 loops in octfapg_universe can and will be vectorized now
after r14-333-g6d4b59a9356ac4 on targets that support multiplication
in the long type. But the testcase does not check vect_long_mult for
that, so this patch corrects that error and now the testcase passes correctly
on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113608
--- Comment #1 from Lehua Ding ---
(In reply to JuzheZhong from comment #0)
> https://godbolt.org/z/srdd4qhdc
>
> #include "riscv_vector.h"
>
> vint32m8_t
> foo (int32_t *__restrict a, int32_t *__restrict b, int32_t *__restrict c,
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113611
Andrew Pinski changed:
What|Removed |Added
Keywords||testsuite-fail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113611
Bug ID: 113611
Summary: [14 Regression] gcc.dg/pr110279-1.c fails on cross
build since gcc-14-5779-g746344dd538
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113610
Andrew Pinski changed:
What|Removed |Added
Keywords||documentation
--- Comment #2 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113610
Andrew Pinski changed:
What|Removed |Added
Component|c |driver
--- Comment #1 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113586
--- Comment #2 from Andrew Pinski ---
My bet is you might be able to reproduce this issue on aarch64 with SVE and
ilp32 but maybe not due to alignment of the stack there is 16 bytes still.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113610
Bug ID: 113610
Summary: Manpage could be more clear about gcc's -e flag
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113609
--- Comment #1 from Hongtao Liu ---
Since they're different modes, CCZ for cmp, but CCS for kortest, it could be
diffcult to optimize it in RA stage by adding alternatives(like we did for
compared to 0). So the easy way could be adding peephole
On 1/25/24 21:28, Nathaniel Shead wrote:
On Wed, Jan 24, 2024 at 03:24:42PM -0500, Jason Merrill wrote:
On 1/20/24 05:45, Nathaniel Shead wrote:
I also included
your change to only add class variable templates to 'pending_statics'
(and the normal 'static_decl's for non-class otherwise) as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113609
Bug ID: 113609
Summary: EQ/NE comparison between avx512 kmask and -1 can be
optimized with kxortest with checking CF.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
On 1/25/24 20:36, Marek Polacek wrote:
Better version:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
Real-world experience shows that -Wdangling-reference triggers for
user-defined std::span-like classes a lot. We can easily avoid that
by considering classes like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #21 from Hongtao Liu ---
typedef unsigned long mp_limb_t;
typedef long mp_size_t;
typedef unsigned long mp_bitcnt_t;
typedef mp_limb_t *mp_ptr;
typedef const mp_limb_t *mp_srcptr;
#define GMP_LIMB_BITS (sizeof(mp_limb_t) * 8)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113608
Bug ID: 113608
Summary: RISC-V: Vector spills after enabling vector abi
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
On Thu, Jan 25, 2024 at 08:37:36PM -0500, Marek Polacek wrote:
> +/* Handle a "non_owning" attribute; arguments as in
> + struct attribute_spec.handler. */
> +
> +tree
> +handle_non_owning_attribute (tree *node, tree name, tree args, int,
> + bool *no_add_attrs)
I
On Wed, Jan 24, 2024 at 03:24:42PM -0500, Jason Merrill wrote:
> On 1/20/24 05:45, Nathaniel Shead wrote:
> > I also included
> > your change to only add class variable templates to 'pending_statics'
> > (and the normal 'static_decl's for non-class otherwise) as otherwise I
> > could imagine that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113576
--- Comment #20 from Hongtao Liu ---
> Note that I wonder how to eliminate redundant maskings? I suppose
> eventually combine tracking nonzero bits where obvious would do
> that? For example for cmp:V4SI we know the bits will be zero but
> I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113600
--- Comment #2 from Hongtao Liu ---
A patch is posted at
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640276.html
Would you give a try to see if it fixes the regression, I don't currently have
a znver4 machine for testing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113607
--- Comment #3 from JuzheZhong ---
I tried trunk GCC to run your case with SPIKE, still didn't reproduce this
issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100638
Andrew Pinski changed:
What|Removed |Added
Summary|FP16 vector compare missed |FP16 (vector) compare
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113607
--- Comment #2 from JuzheZhong ---
I can't reproduce this issue.
Could you test it with this patch applied ?
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643934.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113607
--- Comment #1 from JuzheZhong ---
I can reproduce this issue.
Could you test it with this patch applied ?
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643934.html
Low prio and not a regression. Feel free to ignore till GCC 15.
Bootstrapped/regtested on x86_64-pc-linux-gnu.
-- >8 --
The PR complains that
void do_something(){
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wunused-label"
start:;
#pragma GCC diagnostic pop
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
Since -Wdangling-reference has false positives that can't be
prevented, we should offer an easy way to suppress the warning.
Currently, that is only possible by using a #pragma, either around the
enclosing class or around the
Better version:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
Real-world experience shows that -Wdangling-reference triggers for
user-defined std::span-like classes a lot. We can easily avoid that
by considering classes like
template
struct Span {
T*
On Fri, Jan 26, 2024 at 3:03 AM Roger Sayle wrote:
>
>
> Hi Hongtao,
> Many thanks for the review. Here's a revised version of my patch
> that addresses (most of) the issues you've raised. Firstly the
> handling of zero and all_ones in this function is mostly for
> completeness/documentation,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113325
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-01-26
Severity|normal
Hi,
This patch creates an insn_and_split pattern which helps the duplicated
constant vector replace the source pseudo of store insn in fwprop pass.
Thus the store can be implemented by a single stxvd2x and it eliminates the
unnecessary byte swap insn on P8 LE. The test case shows the
Hi,
This patch replaces rtx_cost with insn_cost in forward propagation.
In the PR, one constant vector should be propagated and replace a
pseudo in a store insn if we know it's a duplicated constant vector.
It reduces the insn cost but not rtx cost. In this case, the kind of
destination operand
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113600
--- Comment #1 from Hongtao Liu ---
Guess it's same issue as PR112879?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29970
Gabriel Ravier changed:
What|Removed |Added
CC||gabravier at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103781
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93370
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.3
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98877
--- Comment #6 from Andrew Pinski ---
In the original testcase, there are still extra movs.
For the testcase in comment #4, it is fixed on the trunk and we now get:
```
fun:
stp x29, x30, [sp, -48]!
mov x29, sp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102066
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102066
Andrew Pinski changed:
What|Removed |Added
CC||pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102055
--- Comment #2 from Andrew Pinski ---
The use of ldr/tbl vs rev64/ext is questionable and depend on if we are inside
a loop or not. In the case of it being inside the loop and there are enough
registers, then using TBL is better on many (not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113599
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113599
--- Comment #6 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:fd620bd3351c6b9821c299035ed17e655d7954b5
commit r14-8439-gfd620bd3351c6b9821c299035ed17e655d7954b5
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113607
Bug ID: 113607
Summary: [14] RISC-V rv64gcv vector: Runtime mismatch at -O3
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On 1/25/24 14:14, Jakub Jelinek wrote:
Hi!
The following testcase reduced from GDB is miscompiled starting with
r14-5503 PR112427 change.
The problem is in the build_m_component_ref hunk, which changed
- datum = fold_build_pointer_plus (fold_convert (ptype, datum), component);
+ datum
When targeting AMD GPUs, the LLVM assembler (and linker) are used.
Two days ago LLVM changed the default for theAMDHSA code object version (COV) from 4 to 5. In principle, we do not
care which COV is used as long as it works; unfortunately,
"mkoffload.cc" also generates an object file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113604
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113606
Bug ID: 113606
Summary: -Wanalyzer-infinite-recursion false positive on code
involving strstr, memset, strnlen and
-D_FORTIFY_SOURCE
Product: gcc
Version: 14.0
Snapshot gcc-11-20240125 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20240125/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
Hello-
May I please ping this small patch? Thanks
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/639467.html
-Lewis
On Wed, Dec 20, 2023 at 8:02 PM Lewis Hyatt wrote:
>
> Hello-
>
> May I please ping this PCH patch? Thanks!
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113604
--- Comment #2 from Andrew Pinski ---
x86 in include/longlong.h defines udiv_qrnnd as:
#define udiv_qrnnd(q, r, n1, n0, dv) \
__asm__ ("div{l} %4" \
: "=a" ((USItype) (q)),
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113604
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113602
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #24 from Jerry DeLisle ---
Currently gfortran does the following:
character(20) :: fmt
character(9) :: buffer
fmt = "(1a1,d0.2,1a1)"
write(buffer,fmt) ">", 3.0, "<"
print *, buffer
fmt = "(1a1,e0.2,1a1)"
write(buffer,fmt) ">",
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113605
Bug ID: 113605
Summary: Fixed-point declaration using an integer where a real
is expected causes a crash
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
On Thu, Jan 25, 2024 at 11:53 AM Björn Schäpers wrote:
>
> Am 23.01.2024 um 23:37 schrieb Ian Lance Taylor:
> > On Thu, Jan 4, 2024 at 2:33 PM Björn Schäpers wrote:
> >>
> >> Am 03.01.2024 um 00:12 schrieb Björn Schäpers:
> >>> Am 30.11.2023 um 20:53 schrieb Ian Lance Taylor:
> On Fri, Jan
On Thu, Jan 25, 2024 at 11:53 AM Björn Schäpers wrote:
>
> Am 23.01.2024 um 23:37 schrieb Ian Lance Taylor:
> > On Thu, Jan 4, 2024 at 2:33 PM Björn Schäpers wrote:
> >>
> >> Am 03.01.2024 um 00:12 schrieb Björn Schäpers:
> >>> Am 30.11.2023 um 20:53 schrieb Ian Lance Taylor:
> On Fri, Jan
May I please ask again about this one? It's just a couple lines, and I
think it fixes an important gap in the logic for #pragma GCC
diagnostic. The PR was not reported by me so I think at least one
other person does care about it :). Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109705
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Dear all,
this is the third patch in a series that addresses dummy arguments
with the VALUE attribute, now handling the passing of NULL actual
arguments. It is based on the refactoring in the previous patch
and reuses the handling of absent arguments.
Regtested on x86_64-pc-linux-gnu. OK for
Thanks for the review!
On Wed, 2024-01-24 at 13:10 -0500, David Malcolm wrote:
> On Thu, 2024-01-11 at 18:42 -0500, Antoni Boucher wrote:
> > Hi.
> > This patch fixes the bug 113343.
> > I'm wondering if there's a better solution than using mpfr.
> > The only other solution I found is
On Thu, Jan 25, 2024 at 08:08:23PM +, Joseph Myers wrote:
> On Wed, 24 Jan 2024, Andi Kleen wrote:
>
> > Implement a C23 clang compatible musttail attribute similar to the earlier
> > C++ implementation in the C parser.
>
> I'd expect diagnostics, and associated tests of those diagnostics,
1 - 100 of 292 matches
Mail list logo
