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=104857
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
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=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=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=97444
--- Comment #1 from Tom de Vries ---
Created attachment 52169
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52169&action=edit
Tentative patch, __atomic_exchange only
Code generated for the generic case:
...
{ // Atomic exchange -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104146
Bug ID: 104146
Summary: FAIL: libgomp.c/../libgomp.c-c++-common/pr96390.c
execution test
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104146
--- Comment #1 from Tom de Vries ---
Adding:
...
/* { dg-xfail-run-if "PR 97102/PR 97106 - .alias not (yet) supported for nvptx"
{ offload_target_nvptx } } */
...
fixes the FAIL.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #8 from Tom de Vries ---
New minimal oacc example:
...
int
main (void)
{
int vectors_max = -1;
#pragma acc parallel\
num_gangs (1) num_workers (1) \
copy (vectors_max)
{
for (in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #9 from Tom de Vries ---
Created attachment 52273
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52273&action=edit
New cuda reproducer
$ ./do.sh
DRIVER SASS, ptxas=-O0:
+ /home/vries/cuda/11.4.3/bin/nvcc vector-max.cu -Wno-dep
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #10 from Tom de Vries ---
[ FTR, T400, driver 470.94 ]
Interestingly, changing the default ptx version to 6.3 makes the minimal
test-case pass, as well as the full parallel-dims.c
The only code changes are shfl -> shfl.sync and vote
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #11 from Tom de Vries ---
(In reply to Tom de Vries from comment #10)
> Rerunning the entire testsuite though shows that the non-32-vector-length
> test-cases are still failing.
Minimal example:
...
int
main (void)
{
#pragma acc para
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #12 from Tom de Vries ---
Created attachment 52285
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52285&action=edit
Cuda reproducer non-32 vector length
[ On T400, driver version 470.94 ]
NVCC SASS:
...
$ ./do.sh
NVCC SASS, p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #13 from Tom de Vries ---
(In reply to Tom de Vries from comment #10)
> [ FTR, T400, driver 470.94 ]
>
> Interestingly, changing the default ptx version to 6.3 makes the minimal
> test-case pass, as well as the full parallel-dims.c
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #14 from Tom de Vries ---
An observation when playing around with vector-length-128-4.c: there are two
ways in which I can make the example pass.
1. add barrier.sync.aligned 0 or membar.cta after first broad-cast receive
2. unroll l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #15 from Tom de Vries ---
(In reply to Tom de Vries from comment #14)
> An observation when playing around with vector-length-128-4.c:
Another observation:
...
$L11:
ld.u64 %r108,[%r109];
st.u64 [%r112],%r108;
setp.lt.u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100428
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100678
--- Comment #3 from Tom de Vries ---
This testcase should be passing since commit
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=e0451f93d9faa13495132f4e246e9bef30b51417
([nvptx] Add some support for .local atomics).
It's possible that we'll put
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100678
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
Tom de Vries changed:
What|Removed |Added
Keywords||testsuite-fail
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364
--- Comment #1 from Tom de Vries ---
(In reply to Thomas Schwinge from comment #0)
> 'nvptx-none/mgomp/libatomic/cas_1_.o' (complete diff):
>
> @@ -113,7 +113,7 @@
> .loc 3 80 9
> or.b64 %r61,%r60,%r39;
> .loc 3 82 11
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364
--- Comment #2 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> What is odd is that the resulting insn is still validated, I would have
> expected that to fail.
Ah, the change is just silently rejected, this makes the problem
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364
--- Comment #3 from Tom de Vries ---
(In reply to Thomas Schwinge from comment #0)
> And, is it correct here to use the non-'atom' replacement, though? '%frame'
> comes from:
>
> .visible .func GOMP_taskwait
> {
> .reg .u64 %stack
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364
--- Comment #4 from Tom de Vries ---
Created attachment 52341
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52341&action=edit
Tentative patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364
--- Comment #5 from Tom de Vries ---
(In reply to Thomas Schwinge from comment #0)
> ... but only seen regressing for:
>
> - Nvidia Tesla K20c, Driver Version: 346.46
> - Nvidia Tesla K20c, Driver Version: 455.38
> - Nvidia Tesla K40c, Dr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104345
--- Comment #2 from Tom de Vries ---
(In reply to Roger Sayle from comment #1)
> The other patches in the "nvptx Boolean" series are:
> patchq3: nvptx: Expand QI mode operations using SI mode instructions.
> https://gcc.gnu.org/pipermail/gcc-pat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005
--- Comment #1 from Tom de Vries ---
Created attachment 52359
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52359&action=edit
Cuda reproducer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005
--- Comment #2 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> Created attachment 52359 [details]
> Cuda reproducer
Filed at https://developer.nvidia.com/nvidia_bug/3527713 as "cvt.u32.u16
sign-extends instead of zero-extends"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005
--- Comment #4 from Tom de Vries ---
(In reply to Jakub Jelinek from comment #3)
> Is some workaround possible, like instead of emitting cvt.u32.u16 do
> cvt.u32.s16 and add explicit and?
This already works:
...
diff --git a/builtin-arith-overfl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005
--- Comment #6 from Tom de Vries ---
(In reply to Jakub Jelinek from comment #5)
> What about u16.u8, u32.u8 and u64.u8 zero extensions?
ptx has no .u8 registers, so there's no straightforward translation of the
example.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005
--- Comment #7 from Tom de Vries ---
(In reply to Tom de Vries from comment #6)
> (In reply to Jakub Jelinek from comment #5)
> > What about u16.u8, u32.u8 and u64.u8 zero extensions?
>
> ptx has no .u8 registers, so there's no straightforward t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005
--- Comment #8 from Tom de Vries ---
I've tried the workaround (posting here only the patch for trunchiqi2, the
pattern that was actually triggered):
...
@@ -424,9 +436,21 @@
[(set (match_operand:QI 0 "nvptx_nonimmediate_operand" "=R,m")
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97006
--- Comment #2 from Tom de Vries ---
With -fno-builtin, mimimized further to:
...
char buffer[100];
int
main (void)
{
unsigned int i = 0xdeadbeef;
__builtin_sprintf (buffer, "%hhx", i);
__builtin_printf ("%s\n", buffer);
__builtin_prin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97006
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #2)
> I'll try to rebuild with
> --enable-newlib-io-c99-formats.
And we run into:
...
In file included from
/home/vries/nvptx/trunk/source-gcc/newlib/libc/include/stdlib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97006
--- Comment #4 from Tom de Vries ---
This fixes it:
...
diff --git a/gcc/testsuite/gcc.dg/tree-ssa/builtin-sprintf.c
b/gcc/testsuite/gcc.dg/tree-ss
a/builtin-sprintf.c
index f90558e9b7ee..9368a2e0e50a 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104422
Bug ID: 104422
Summary: nvptx: for-3.exe fail with driver 390.x
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
Bug ID: 104423
Summary: [libgomp, testsuite] Add means to do accelerator-only
testing in libgomp
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: enhan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440
Bug ID: 104440
Summary: nvptx: FAIL: gcc.c-torture/execute/pr53465.c
execution test
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440
Tom de Vries changed:
What|Removed |Added
Target||nvptx
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440
--- Comment #4 from Tom de Vries ---
(In reply to Andrew Pinski from comment #2)
> I thought there was another bug that reported a similar issue.
You mean related to nvptx, or in general?
FWIW, I do remember looking at this issue before in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97006
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |12.0
Component|target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104364
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104422
--- Comment #2 from Tom de Vries ---
Hmm, I reran on a(In reply to Tom de Vries from comment #0)
> #pragma distribute simd
omp missing ... I need to reproduce this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #1 from Tom de Vries ---
One of the dimensions that I test is env var GOMP_NVPTX_JIT, with values:
- -O0, and
- default (using unset GOMP_NVPTX_JIT), which supposedly is -O4.
Looking at f.i. test-case for-3.c, compilation takes 3 mi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104422
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #0)
> While testing libgomp using legacy driver 390.x on a maxwell card, Quadro
> K620 I ran into a for-3.exe execution failure.
Reproduced with 390.147 driver on pasca
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104283
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #3 from Tom de Vries ---
(In reply to Thomas Schwinge from comment #2)
> For OpenMP test cases, we'd either have to manually mark them up (error
> prone and generally ugly), or scan the source file(s) (error prone and
> generally ugl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104422
--- Comment #4 from Tom de Vries ---
(In reply to Tom de Vries from comment #3)
> Reproduces both with and without GOMP_NVPTX_JIT=-O0.
Pff, that was an artefact of having bumped the default ptx isa to 6.3.
So, let's try again ...
Reproduced w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104422
--- Comment #5 from Tom de Vries ---
Still on GT1030, does not reproduce with 470.x, neither the minimal nor the
complete for-3.c.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104422
--- Comment #6 from Tom de Vries ---
(In reply to Tom de Vries from comment #5)
> Still on GT1030, does not reproduce with 470.x, neither the minimal nor the
> complete for-3.c.
And the same for 510.x.
So, I'm parking this for now. This may w
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104456
Bug ID: 104456
Summary: nvptx: prevent_branch_around_nothing doesn't handle
asm ("")
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97005
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104489
Bug ID: 104489
Summary: nvptx, sm_53: internal compiler error: in
gen_rtx_SUBREG, at emit-rtl.cc:1022
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104489
--- Comment #1 from Tom de Vries ---
Created attachment 52407
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52407&action=edit
reproducer
$ xgcc -B/home/vries/nvptx/trunk/build-gcc/./gcc/ -O2 -S mulhc3.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104456
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |12.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104489
Tom de Vries changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #4 from Tom de Vries ---
Created attachment 52416
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52416&action=edit
[libgomp, testsuite, nvptx] Add GOMP_NVPTX_JIT_ITER (libgomp.c/c.exp only)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104423
--- Comment #5 from Tom de Vries ---
Created attachment 52438
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52438&action=edit
Tentative patch (GOMP_TARGET_ENV_ITER)
A more generic solution using env var GOMP_TARGET_ENV_ITER, which allows
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440
--- Comment #8 from Tom de Vries ---
Created attachment 52456
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52456&action=edit
Tentative patch, introducing -minit-regs=<0|1|2>
This patch fixes the problem, and survived a standalone build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440
--- Comment #9 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> Tentative patch that fixes example:
> ...
> diff --git a/gcc/config/nvptx/nvptx.cc b/gcc/config/nvptx/nvptx.cc
> index 5b26c0f4c7dd..4dc154434853 100644
> --- a/gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440
--- Comment #10 from Tom de Vries ---
A good thing to note at this point: why doesn't init-regs work here?
The pass works per insn, and when hitting the insn with the problematic use:
...
(gdb) call debug_rtx (insn)
(insn 18 17 19 4 (set (reg/v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104580
Bug ID: 104580
Summary: [nvptx] Use prevent_branch_around_nothing only when
necessary
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104580
--- Comment #1 from Tom de Vries ---
Created attachment 52457
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52457&action=edit
Tentative patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103095
Bug ID: 103095
Summary: Option to force no overalignment
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: other
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89262
Tom de Vries changed:
What|Removed |Added
Target Milestone|--- |10.2
--- Comment #1 from Tom de Vries --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103095
Tom de Vries changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103436
Bug ID: 103436
Summary: gnatD debug info refers to original rather than
generated file
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99932
--- Comment #7 from Tom de Vries ---
(In reply to Tom de Vries from comment #6)
> (In reply to Tom de Vries from comment #5)
> > FIled https://developer.nvidia.com/nvidia_bug/3299227
>
> Nvidia reported it will be fixed in the next major cuda re
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100428
--- Comment #4 from Tom de Vries ---
FTR, reproduces with driver version 470.86 on Quadro M1200 and GeForce GT 1030.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102216
Bug ID: 102216
Summary: False positive warray-bounds with -O2
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optim
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=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=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=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=101452
Bug ID: 101452
Summary: [debug, dwarf-5] undefined static member removed by
-feliminate-unused-debug-symbols
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101452
--- Comment #2 from Tom de Vries ---
(In reply to Richard Biener from comment #1)
> do you have an idea why it works with -gdwarf-4 but not -gdwarf-5?
If we do with n == 4 and n == 5:
...
$ rm -f *.c.* ; ./install/bin/g++ test.c -c -g -gdwarf-$
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101470
Bug ID: 101470
Summary: Support -gline-tables-only
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: debug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101470
--- Comment #1 from Tom de Vries ---
Created attachment 51161
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51161&action=edit
Demonstrator patch
I wrote a demonstrator patch that makes the two mentioned differences
disappear.
It also dr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101575
Bug ID: 101575
Summary: [gcc-11, -gdwarf-4] Missing .file directive causes
invalid line info
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101575
--- Comment #2 from Tom de Vries ---
(In reply to Eric Botcazou from comment #1)
> Not going to be fixed,
Because ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101575
--- Comment #5 from Tom de Vries ---
(In reply to Bernd Edlinger from comment #4)
> Hi,
>
> I think my commit e69ac020372 ("Add line debug info for virtual thunks")
> has a mitigating effect on this test case:
> due to such functions have DECL_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101575
--- Comment #6 from Tom de Vries ---
(In reply to Eric Botcazou from comment #3)
> > Because ?
>
> No straightforward solution in DWARF < 5 and, therefore, not worth the
> hassle.
How about backporting the commit to gcc-11-branch? WDYT?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101598
Bug ID: 101598
Summary: [debug, ada] .loc generated for defs__struct1IP
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101575
--- Comment #9 from Tom de Vries ---
(In reply to Eric Botcazou from comment #7)
> (> More specifically, it's gone because we have:
> > ...
> > $ more defs.s
> > .file "defs.adb"
> > .text
> > .Ltext0:
> > .align 2
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101598
--- Comment #1 from Tom de Vries ---
FWIW, this works for me:
...
$ git diff
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 82783c4968b..0e21775041c 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -28390,6 +28390,8 @@ dwarf2out_sourc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101598
--- Comment #3 from Tom de Vries ---
(In reply to Tom de Vries from comment #1)
> FWIW, this works for me:
And, doesn't reintroduce PR101575 on trunk.
AFAIU, the solution suggested in PR101575 comment 8 of setting the
DECL_SOURCE_LOCATION for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101598
--- Comment #4 from Tom de Vries ---
(In reply to Bernd Edlinger from comment #2)
> Yes, but it wont fix dwarf-4 and also not the case
> when this is not the first function. then we'll
> have the .loc from the previous function extend to this on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101633
Bug ID: 101633
Summary: [debug] DW_TAG_subrange_type missing DW_AT_upper_bound
Product: gcc
Version: 7.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101633
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101633
--- Comment #2 from Tom de Vries ---
https://gcc.gnu.org/pipermail/gcc-patches/2017-May/474657.html :
...
>> 2017-05-15 Richard Biener
>>
>> * dwarf2out.c (loc_list_from_tree_1): Do not create
>> DW_OP_GNU_variable_value for DECL_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101643
Bug ID: 101643
Summary: [debug, ada] packed array not described as packed
Product: gcc
Version: 7.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101643
Tom de Vries changed:
What|Removed |Added
Resolution|--- |FIXED
Keywords|
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=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
--- 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 #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=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=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=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
--- 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
301 - 400 of 418 matches
Mail list logo
