https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117224
Bug ID: 117224
Summary: warning states "this" is explicit by-copy capture but
it's an explicit by-reference capture
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115272
--- Comment #5 from Tom de Vries ---
(In reply to Tom de Vries from comment #4)
> With this patch:
So, would this approach be acceptable?
If so, I can put effort into doing a proper submission.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988
--- Comment #4 from Tom de Vries ---
(In reply to Tom Tromey from comment #2)
> Also, I see the "__unknown__" there now -- better IMO to let gdb synthesize
> a name instead.
Attempt to synthesize the name in gcc:
...
commit d2b7f315ad976ff18c71e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93988
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
--- Comment #3 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115272
--- Comment #4 from Tom de Vries ---
With this patch:
...
diff --git a/gcc/dwarf2out.cc b/gcc/dwarf2out.cc
index 8ec3856873e..ea3318396e0 100644
--- a/gcc/dwarf2out.cc
+++ b/gcc/dwarf2out.cc
@@ -13247,6 +13247,7 @@ base_type_die (tree type, bool
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115272
--- Comment #3 from Tom de Vries ---
(In reply to Richard Biener from comment #2)
> (In reply to Richard Biener from comment #1)
> > How does it work for 'double' vs. 'long double' themselves?
> >
> > <1><32>: Abbrev Number: 3 (DW_TAG_base_typ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115272
Bug ID: 115272
Summary: [debug] complex type is hard to related back to base
type
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111409
Tom de Vries changed:
What|Removed |Added
CC||hjl.tools at gmail dot com
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87472
Tom de Vries changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111409
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
Target Milest
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |15.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
--- Comment #7 from Tom de Vries ---
Submitted here ( https://gcc.gnu.org/pipermail/gcc-patches/2024-May/651586.html
).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
--- Comment #6 from Tom de Vries ---
(In reply to Jakub Jelinek from comment #5)
> Just make it if (dwarf_split_debug_info) then?
That works as well indeed:
...
diff --git a/gcc/dwarf2out.cc b/gcc/dwarf2out.cc
index eedb13bb069..70b7f5f42cd 100
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
--- Comment #4 from Tom de Vries ---
(In reply to Richard Biener from comment #3)
> And with -gstrict-dwarf -gdwarf-4?
With:
...
$ gcc.sh -gdwarf-4 -gsplit-dwarf /data/vries/hello.c -g3 -gstrict-dwarf
...
we get:
...
.section.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
--- Comment #2 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> Looking at the source code, I wonder if this would fix it:
> ...
> diff --git a/gcc/dwarf2out.cc b/gcc/dwarf2out.cc
> index eedb13bb069..045858bf638 100644
> --- a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
--- Comment #1 from Tom de Vries ---
Looking at the source code, I wonder if this would fix it:
...
diff --git a/gcc/dwarf2out.cc b/gcc/dwarf2out.cc
index eedb13bb069..045858bf638 100644
--- a/gcc/dwarf2out.cc
+++ b/gcc/dwarf2out.cc
@@ -29045,7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115066
Bug ID: 115066
Summary: [debug, gsplit-dwarf, gdwarf-4, g3]
DW_MACRO_define_strp used for debug_str_offsets index
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113599
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112565
--- Comment #1 from Tom de Vries ---
(In reply to Anonymous from comment #0)
> Tom de Vries suggests that this issue may be attributed to a GCC
> optimization bug.
I do not.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110799
--- Comment #7 from Tom de Vries ---
(In reply to Alexander Monakov from comment #5)
> This trips Valgrind's data race detector (valgrind --tool=helgrind) too. So
> I don't think checking SANITIZE_THREAD is the correct approach.
Can you elabora
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110799
--- Comment #6 from Tom de Vries ---
(In reply to rguent...@suse.de from comment #4)
> I'm suggesting to not fix it ;)
Can you explain why ?
It doesn't look difficult to fix to me, and I don't see any downsides.
> That said, is TSAN a useful
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110799
--- Comment #2 from Tom de Vries ---
(In reply to Richard Biener from comment #1)
> We consider introducing load data races OK, what's the difference here?
This is a load vs. store data race.
> There are other passes that would do similar thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110799
Bug ID: 110799
Summary: [tsan] False positive due to -fhoist-adjacent-loads
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109708
Bug ID: 109708
Summary: [c, doc] wdangling-pointer example broken
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108600
--- Comment #4 from Tom de Vries ---
(In reply to Tom de Vries from comment #0)
> Note that for for instance gdb test-case gdb.ada/ref_param.exp, this
> convention was broken for gcc 7.5.0 (and I don't know how much earlier), and
> my current gu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108615
Tom de Vries changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108615
Bug ID: 108615
Summary: Incorrect prologue marker in line table
Product: gcc
Version: 10.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108600
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> (In reply to Tom de Vries from comment #1)
> > Created attachment 54371 [details]
>
> We probably don't want to emit in all cases, maybe limiting to
> "dwarf_ver
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47471
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
--- Comment #24
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108600
--- Comment #2 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> Created attachment 54371 [details]
We probably don't want to emit in all cases, maybe limiting to
"dwarf_version >= 3", or "!dwarf_strict || dwarf_version >= 3".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108600
--- Comment #1 from Tom de Vries ---
Created attachment 54371
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54371&action=edit
tentative patch
Tentative patch.
For hello.c, for the -gas-loc-support case it gives us:
...
$ gcc -g ~/hello.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108600
Bug ID: 108600
Summary: Use DW_LNS_set_prologue_end
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: debug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108098
--- Comment #1 from Tom de Vries ---
(In reply to Thomas Schwinge from comment #0)
> $ nvidia-smi
> [...]
> | NVIDIA-SMI 440.33.01Driver Version: 440.33.01CUDA Version: 10.2
> [...]
> | 0 Tesla K80 [...]
> [..
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107909
Bug ID: 107909
Summary: [powerpc64le, debug] Incorrect call site location due
to nop after call insn
Product: gcc
Version: 7.5.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87741
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
Stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99555
--- Comment #17 from Tom de Vries ---
(In reply to Thomas Schwinge from comment #14)
> > That's with a Nvidia Tesla K20c GPU, Driver Version: 346.46.
> > As that version is "a bit old", I shall first update this, before we spend
> > any further t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105772
--- Comment #2 from Tom de Vries ---
As background info, I'm proposing a patch for gdb to have the
architecture-specific prologue skipper skip over the get_pc_thunk call:
https://sourceware.org/pipermail/gdb-patches/2022-May/189563.html , which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105772
Bug ID: 105772
Summary: [debug, i386] sched2 moves get_pc_thunk call past
debug_insn
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104893
Tom de Vries changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104857
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104714
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |12.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105096
Bug ID: 105096
Summary: --target-help not an alias for --help=target
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: dr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53037
Tom de Vries changed:
What|Removed |Added
CC||vries at gcc dot gnu.org
--- Comment #43
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81909
Tom de Vries changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81728
Tom de Vries changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104818
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105042
Tom de Vries changed:
What|Removed |Added
Severity|normal |enhancement
--- Comment #8 from Tom de V
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105075
--- Comment #6 from Tom de Vries ---
Created attachment 52698
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52698&action=edit
Demonstrator patch with stepping stone patterns for combine
(In reply to Tom de Vries from comment #2)
> Also,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105014
--- Comment #6 from Tom de Vries ---
Reproducer filed at https://github.com/vries/nvidia-bugs/tree/master/shift-and
PR filed at nvidia ( https://developer.nvidia.com/nvidia_bug/3585290 ).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105075
Tom de Vries changed:
What|Removed |Added
Attachment #52693|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105075
--- Comment #2 from Tom de Vries ---
AFAIU, at gimple level support is limited to vectors, so that doesn't help to
generate the insn for the simple, scalar case.
It would be nice if combine could generate it and we wouldn't have to use a
peepho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105075
--- Comment #1 from Tom de Vries ---
Created attachment 52693
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52693&action=edit
Demonstrator patch
This patch adds:
- modeling of insn sad.u32 in the .md file
- peephole2 to generate it
(wh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105075
Bug ID: 105075
Summary: [nvptx] Generate sad insn (sum of absolute
differences)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105042
--- Comment #5 from Tom de Vries ---
(In reply to Richard Biener from comment #1)
> Doesn't whatever driver/library API we use from libgomp to invoke workloads
> report actual errors? Maybe we need to improve there.
This:
...
libgomp: cuStream
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105042
--- Comment #4 from Tom de Vries ---
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/592275.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105042
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> (In reply to Richard Biener from comment #1)
> > Doesn't whatever driver/library API we use from libgomp to invoke workloads
> > report actual errors? Maybe we ne
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105014
--- Comment #5 from Tom de Vries ---
Minimal test-case:
...
void __attribute__((noinline)) foo (unsigned long long d0) {
unsigned long long __a;
__a = 0x38;
for (; __a > 0; __a -= 8)
if (((d0 >> __a) & 0xff) != 0)
break;
__bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105011
Tom de Vries changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105042
--- Comment #2 from Tom de Vries ---
(In reply to Richard Biener from comment #1)
> Doesn't whatever driver/library API we use from libgomp to invoke workloads
> report actual errors? Maybe we need to improve there.
Good point, it reported som
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105014
--- Comment #4 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> With -O0 JIT instead:
Also OK with JIT -O1, problems start at JIT -O2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105011
--- Comment #3 from Tom de Vries ---
Submitted fix :
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/592211.html
Though without changelog, apparently.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105042
Bug ID: 105042
Summary: [libgomp, GOMP_NVPTX_JIT=-O0] Openacc testsuite
failures when X runs on nvidia driver
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Se
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105019
--- Comment #6 from Tom de Vries ---
(In reply to Tom de Vries from comment #4)
> OK, I think this is the pattern:
> ...
> $ cat gcc/testsuite/gcc.target/nvptx/alias-5.c
FTR, same thing if I use static functions:
...
static void __attribute__((
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105019
--- Comment #5 from Tom de Vries ---
Creating a CUDA example is hampered by the fact that there's no symbol alias
support, AFAICT.
I'd like to write something like:
...
__device__ void __foo ()
{
printf ("__foo\n");
}
__device__ void foo () _
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105019
--- Comment #4 from Tom de Vries ---
OK, I think this is the pattern:
...
$ cat gcc/testsuite/gcc.target/nvptx/alias-5.c
/* { dg-do link } */
/* { dg-do run { target runtime_ptx_isa_version_6_3 } } */
/* { dg-options "-save-temps -malias -mptx=6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105019
--- Comment #3 from Tom de Vries ---
Aliases in failing .exe:
...
$ strings declare_target-1.exe | grep "\.alias"
.alias gomp_ialias_GOMP_taskgroup_start,GOMP_taskgroup_start;
.alias gomp_ialias_GOMP_taskgroup_end,GOMP_taskgroup_end;
.alias
gomp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105019
--- Comment #2 from Tom de Vries ---
Aliases in libgomp.a:
...
$ grep "\.alias"
build-gcc-offload-nvptx-none/nvptx-none/mgomp/libgomp/.libs/libgomp.a
.alias gomp_ialias_GOMP_loop_runtime_next,GOMP_loop_runtime_next;
.alias gomp_ialias_GOMP_loop_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105019
--- Comment #1 from Tom de Vries ---
To trigger:
...
diff --git a/gcc/config/nvptx/nvptx.cc b/gcc/config/nvptx/nvptx.cc
index 87efc23bd96..8bf9ea90a77 100644
--- a/gcc/config/nvptx/nvptx.cc
+++ b/gcc/config/nvptx/nvptx.cc
@@ -245,6 +245,9 @@ def
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105019
Bug ID: 105019
Summary: [nvptx] malias in libgomp results in "Internal error:
reference to deleted section"
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Seve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105014
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> (In reply to Tom de Vries from comment #0)
> > On a quadro k2000 with driver 470.103.01, I run into:
>
> So, sm_30.
>
> > ...
> > FAIL: gcc.dg/pr97459-1.c execut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105014
--- Comment #2 from Tom de Vries ---
(In reply to Tom de Vries from comment #0)
> On a quadro k2000 with driver 470.103.01, I run into:
So, sm_30.
> ...
> FAIL: gcc.dg/pr97459-1.c execution test
Reproduced on geforce gt710 (sm_35), with same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105018
--- Comment #2 from Tom de Vries ---
As mentioned before by amonakov, a possibility is to add alias support to the
nvptx-tools linker, and use that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105018
--- Comment #1 from Tom de Vries ---
(In reply to Tom de Vries from comment #0)
> Aliases to aliases are not supported (see libgomp.c-c++-common/pr96390.c).
> This is currently not prohibited by the compiler, but with the driver link we
> run in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105018
Bug ID: 105018
Summary: [nvptx] Need better alias support
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97106
Tom de Vries changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97106
Bug 97106 depends on bug 97102, which changed state.
Bug 97102 Summary: [nvptx] PTX JIT compilation failed when using aliases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97102
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97102
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |12.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98215
Tom de Vries changed:
What|Removed |Added
Severity|normal |enhancement
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104916
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |12.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104916
Tom de Vries changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104783
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104957
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |12.0
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104925
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105016
--- Comment #3 from Tom de Vries ---
In libgcc.h, I see:
...
#define __udivmoddi4__NDW(udivmod,4)
...
and for LIBGCC2_UNITS_PER_WORD == 8 we have:
...
#define __NDW(a,b) __ ## a ## ti ## b
...
So, AFAICT it's possible that __udivmoddi4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105016
--- Comment #1 from Tom de Vries ---
Created attachment 52662
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52662&action=edit
test-case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105016
Bug ID: 105016
Summary: [libgcc, TARGET_HAS_NO_HW_DIVIDE] Incorrect result for
__udivmodti4
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105014
--- Comment #1 from Tom de Vries ---
First FAIL minimizes to:
...
typedef __uint128_t T;
union u {
T t;
struct {
unsigned long long x;
unsigned long long y;
} xy;
};
#define PRINT(VAR) \
do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105014
Bug ID: 105014
Summary: [nvptx] FAIL: gcc.dg/pr97459-1.c execution test
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105011
--- Comment #2 from Tom de Vries ---
Even better:
...
diff --git a/libatomic/tas_n.c b/libatomic/tas_n.c
index d0d8c283b495..65eaa7753a51 100644
--- a/libatomic/tas_n.c
+++ b/libatomic/tas_n.c
@@ -73,7 +73,7 @@ SIZE(libat_test_and_set) (UTYPE *m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105011
--- Comment #1 from Tom de Vries ---
(In reply to Tom de Vries from comment #0)
> It should probably do something like:
> ...
> return (woldval & wval) != 0;
> ...
Indeed, that fixes the FAILs.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105011
Bug ID: 105011
Summary: [nvptx] FAIL: gcc.dg/atomic/stdatomic-flag-2.c -O1
execution test
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105001
--- Comment #1 from Tom de Vries ---
Interesting.
Can you compare dump files to see where the difference comes from?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104936
Tom de Vries changed:
What|Removed |Added
Severity|normal |enhancement
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104991
Bug ID: 104991
Summary: [nvptx] Simplify muniform-simt transformation
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104968
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104952
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104968
--- Comment #6 from Tom de Vries ---
(In reply to Tom de Vries from comment #5)
> This patch fixes the ICE at openmp level:
> ...
> diff --git a/gcc/gimplify.cc b/gcc/gimplify.cc
> index 139a0de6100..19af384c634 100644
> --- a/gcc/gimplify.cc
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104957
Tom de Vries changed:
What|Removed |Added
Severity|normal |enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104968
Tom de Vries changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
1 - 100 of 417 matches
Mail list logo
