[PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Joseph Faulls]

[-- Attachment #1: Type: text/plain, Size: 3754 bytes --]

Relaxations can cause the gp to move after it has been decided to gp
relax. Against an absolute symbol, the distance may change such that the
offset can no longer fit in the 12-bit immediate field.

bfd/
        * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against and ABS
          symbol if it is far away.
ld/
        * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
        * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
---
bfd/elfnn-riscv.c                            | 12 ++++++++++++
ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
5 files changed, 35 insertions(+)
create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s

diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c
index 09aa7be225e..79e29e8b272 100644
--- a/bfd/elfnn-riscv.c
+++ b/bfd/elfnn-riscv.c
@@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
              max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
              htab->max_alignment_for_gp = max_alignment;
            }
+         /* If the symbol is in the abs section, relaxation could cause the gp
+          * to move such that the gp relocation is no longer possible.
+          * Conservatively half the allowed distance, as it cannot be that
+          * gp moves more than this, i.e. more than half the instructions be
+          * deleted due to relaxation.  Do this by adjusting reserve_size.  */
+         if (sym_sec->output_section == bfd_abs_section_ptr)
+           {
+             if (symval >= gp)
+               reserve_size += (symval - gp) / 2;
+             else
+               reserve_size += (gp - symval) / 2;
+           }
        }
     }

diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
new file mode 100644
index 00000000000..a018bb3a50a
--- /dev/null
+++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
@@ -0,0 +1,3 @@
+.section .data
+.globl sym
+.set sym,0x10804
diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
new file mode 100644
index 00000000000..2c7ab3a2579
--- /dev/null
+++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
@@ -0,0 +1,14 @@
+#source: gp-relax-abs.s
+#source: gp-relax-abs-sym.s
+#as: -march=rv64ic -mabi=lp64
+#ld: -Tcode-model-01.ld -melf64lriscv
+#objdump: -d
+
+.*:[   ]+file format .*
+
+Disassembly of section \.text:
+
+[0-9a-f]+ <_start>:
+.*auipc.*
+.*lw.*# [0-9a-f]* <sym>
+#pass
diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
new file mode 100644
index 00000000000..db2103bafd1
--- /dev/null
+++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
@@ -0,0 +1,5 @@
+.text
+.global _start
+_start:
+    auipc t0, %pcrel_hi(sym)
+    lw t0, %pcrel_lo(_start)(t0)
diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
index 947a266ba72..a53a2758991 100644
--- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
+++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
@@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
     run_dump_test "attr-merge-priv-spec-failed-06"
     run_dump_test "attr-phdr"
     run_dump_test "relax-max-align-gp"
+    run_dump_test "gp-relax-abs"
     run_dump_test "uleb128"
     run_ld_link_tests [list \
        [list "Weak reference 32" "-T weakref.ld -m[riscv_choose_ilp32_emul]" "" \
--
2.34.1

Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Andreas Schwab]

On Jul 27 2023, Joseph Faulls wrote:

>         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against and ABS

s/and/an/

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Palmer Dabbelt]

On Thu, 27 Jul 2023 09:48:24 PDT (-0700), Joseph.Faulls@imgtec.com wrote:
> Relaxations can cause the gp to move after it has been decided to gp
> relax. Against an absolute symbol, the distance may change such that the
> offset can no longer fit in the 12-bit immediate field.
>
> bfd/
>         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against and ABS
>           symbol if it is far away.
> ld/
>         * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
>         * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
> ---
> bfd/elfnn-riscv.c                            | 12 ++++++++++++
> ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
> ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
> ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
> ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
> 5 files changed, 35 insertions(+)
> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>
> diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c
> index 09aa7be225e..79e29e8b272 100644
> --- a/bfd/elfnn-riscv.c
> +++ b/bfd/elfnn-riscv.c
> @@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
>               max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
>               htab->max_alignment_for_gp = max_alignment;
>             }
> +         /* If the symbol is in the abs section, relaxation could cause the gp
> +          * to move such that the gp relocation is no longer possible.

I'm not quite sure what you mean by GP moving -- GP's the register, so 
it doesn't have a value until runtime.  GP is meant to equal 
__global_pointer$, but that's usually a data symbol and thus doesn't 
move as a result of relaxation.

We do have some other issues related to SHN_ABS (for example position 
independent vs PC relative stuff), so it's possible there's some other 
bug here?

> +          * Conservatively half the allowed distance, as it cannot be that
> +          * gp moves more than this, i.e. more than half the instructions be
> +          * deleted due to relaxation.  Do this by adjusting reserve_size.  */
> +         if (sym_sec->output_section == bfd_abs_section_ptr)
> +           {
> +             if (symval >= gp)
> +               reserve_size += (symval - gp) / 2;
> +             else
> +               reserve_size += (gp - symval) / 2;

We can have more than a factor of two from relaxation, for example from 
alignment.  If a hueristic is all we can do then I guess we'll have to 
live with it, but I think I'd want to understand the movement 

> +           }
>         }
>      }
>
> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> new file mode 100644
> index 00000000000..a018bb3a50a
> --- /dev/null
> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> @@ -0,0 +1,3 @@
> +.section .data
> +.globl sym
> +.set sym,0x10804
> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> new file mode 100644
> index 00000000000..2c7ab3a2579
> --- /dev/null
> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> @@ -0,0 +1,14 @@
> +#source: gp-relax-abs.s
> +#source: gp-relax-abs-sym.s
> +#as: -march=rv64ic -mabi=lp64
> +#ld: -Tcode-model-01.ld -melf64lriscv
> +#objdump: -d
> +
> +.*:[   ]+file format .*
> +
> +Disassembly of section \.text:
> +
> +[0-9a-f]+ <_start>:
> +.*auipc.*
> +.*lw.*# [0-9a-f]* <sym>
> +#pass
> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> new file mode 100644
> index 00000000000..db2103bafd1
> --- /dev/null
> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> @@ -0,0 +1,5 @@
> +.text
> +.global _start
> +_start:
> +    auipc t0, %pcrel_hi(sym)
> +    lw t0, %pcrel_lo(_start)(t0)
> diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> index 947a266ba72..a53a2758991 100644
> --- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> +++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> @@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
>      run_dump_test "attr-merge-priv-spec-failed-06"
>      run_dump_test "attr-phdr"
>      run_dump_test "relax-max-align-gp"
> +    run_dump_test "gp-relax-abs"
>      run_dump_test "uleb128"
>      run_ld_link_tests [list \
>         [list "Weak reference 32" "-T weakref.ld -m[riscv_choose_ilp32_emul]" "" \

Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Nelson Chu]

[-- Attachment #1: Type: text/plain, Size: 6060 bytes --]

Relaxation should shrink the text, but since the default linker script has
huge data segment alignment, data after the segment alignment shouldn't be
affected and shrinked, so ideally  it should be safe by using default
linker script.

Do you have a reduced test that shows we still have a chance to get the
relax error by using the default linker script?

On Fri, Jul 28, 2023 at 5:08 AM Palmer Dabbelt <palmer@rivosinc.com> wrote:

> On Thu, 27 Jul 2023 09:48:24 PDT (-0700), Joseph.Faulls@imgtec.com wrote:
> > Relaxations can cause the gp to move after it has been decided to gp
> > relax. Against an absolute symbol, the distance may change such that the
> > offset can no longer fit in the 12-bit immediate field.
> >
> > bfd/
> >         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against
> and ABS
> >           symbol if it is far away.
> > ld/
> >         * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
> >         * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
> > ---
> > bfd/elfnn-riscv.c                            | 12 ++++++++++++
> > ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
> > ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
> > ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
> > ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
> > 5 files changed, 35 insertions(+)
> > create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> > create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> > create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> >
> > diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c
> > index 09aa7be225e..79e29e8b272 100644
> > --- a/bfd/elfnn-riscv.c
> > +++ b/bfd/elfnn-riscv.c
> > @@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
> >               max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
> >               htab->max_alignment_for_gp = max_alignment;
> >             }
> > +         /* If the symbol is in the abs section, relaxation could cause
> the gp
> > +          * to move such that the gp relocation is no longer possible.
>
> I'm not quite sure what you mean by GP moving -- GP's the register, so
> it doesn't have a value until runtime.  GP is meant to equal
> __global_pointer$, but that's usually a data symbol and thus doesn't
> move as a result of relaxation.
>
> We do have some other issues related to SHN_ABS (for example position
> independent vs PC relative stuff), so it's possible there's some other
> bug here?
>
> > +          * Conservatively half the allowed distance, as it cannot be
> that
> > +          * gp moves more than this, i.e. more than half the
> instructions be
> > +          * deleted due to relaxation.  Do this by adjusting
> reserve_size.  */
> > +         if (sym_sec->output_section == bfd_abs_section_ptr)
> > +           {
> > +             if (symval >= gp)
> > +               reserve_size += (symval - gp) / 2;
> > +             else
> > +               reserve_size += (gp - symval) / 2;
>
> We can have more than a factor of two from relaxation, for example from
> alignment.  If a hueristic is all we can do then I guess we'll have to
> live with it, but I think I'd want to understand the movement
>

An extreme case is that all the instruction can be relaxed without any huge
alignments between text and data, so I guess that's probably why the half
of distance comes from.  If the default linker script may cause the
problem, then we will need to know more details and try to resolve it.  But
if this only occurs without the default linker script, then I will suggest
users disable that relax patterns by the .norelax directive, or related
options of compiler/assembler/linker.  Or maybe we can have an option for
users to reject gp relax when meeting abs symbols, if without using default
linker script.  However, please give a reduced case by using default linker
script that will be broken in detailed, thanks a lot.

Nelson


> > +           }
> >         }
> >      }
> >
> > diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> > new file mode 100644
> > index 00000000000..a018bb3a50a
> > --- /dev/null
> > +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> > @@ -0,0 +1,3 @@
> > +.section .data
> > +.globl sym
> > +.set sym,0x10804
> > diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> > new file mode 100644
> > index 00000000000..2c7ab3a2579
> > --- /dev/null
> > +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> > @@ -0,0 +1,14 @@
> > +#source: gp-relax-abs.s
> > +#source: gp-relax-abs-sym.s
> > +#as: -march=rv64ic -mabi=lp64
> > +#ld: -Tcode-model-01.ld -melf64lriscv
> > +#objdump: -d
> > +
> > +.*:[   ]+file format .*
> > +
> > +Disassembly of section \.text:
> > +
> > +[0-9a-f]+ <_start>:
> > +.*auipc.*
> > +.*lw.*# [0-9a-f]* <sym>
> > +#pass
> > diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> > new file mode 100644
> > index 00000000000..db2103bafd1
> > --- /dev/null
> > +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> > @@ -0,0 +1,5 @@
> > +.text
> > +.global _start
> > +_start:
> > +    auipc t0, %pcrel_hi(sym)
> > +    lw t0, %pcrel_lo(_start)(t0)
> > diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> > index 947a266ba72..a53a2758991 100644
> > --- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> > +++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> > @@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
> >      run_dump_test "attr-merge-priv-spec-failed-06"
> >      run_dump_test "attr-phdr"
> >      run_dump_test "relax-max-align-gp"
> > +    run_dump_test "gp-relax-abs"
> >      run_dump_test "uleb128"
> >      run_ld_link_tests [list \
> >         [list "Weak reference 32" "-T weakref.ld
> -m[riscv_choose_ilp32_emul]" "" \
>

Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Nelson Chu]

[-- Attachment #1: Type: text/plain, Size: 6660 bytes --]

Maybe, if the shrink code is more than the data segment alignment in the
default linker script (0x1000), then probably still have a chance to get
the truncated gp by using default linker script...  I will suggest if that
is so, then we just have a linker option to disallow/allow the gp relax for
any abs symbol, that should be more intuitive.

On Fri, Jul 28, 2023 at 9:02 AM Nelson Chu <nelson@rivosinc.com> wrote:

> Relaxation should shrink the text, but since the default linker script has
> huge data segment alignment, data after the segment alignment shouldn't be
> affected and shrinked, so ideally  it should be safe by using default
> linker script.
>
> Do you have a reduced test that shows we still have a chance to get the
> relax error by using the default linker script?
>
> On Fri, Jul 28, 2023 at 5:08 AM Palmer Dabbelt <palmer@rivosinc.com>
> wrote:
>
>> On Thu, 27 Jul 2023 09:48:24 PDT (-0700), Joseph.Faulls@imgtec.com wrote:
>> > Relaxations can cause the gp to move after it has been decided to gp
>> > relax. Against an absolute symbol, the distance may change such that the
>> > offset can no longer fit in the 12-bit immediate field.
>> >
>> > bfd/
>> >         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against
>> and ABS
>> >           symbol if it is far away.
>> > ld/
>> >         * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
>> >         * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
>> > ---
>> > bfd/elfnn-riscv.c                            | 12 ++++++++++++
>> > ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
>> > ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
>> > ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
>> > ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
>> > 5 files changed, 35 insertions(+)
>> > create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> > create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> > create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> >
>> > diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c
>> > index 09aa7be225e..79e29e8b272 100644
>> > --- a/bfd/elfnn-riscv.c
>> > +++ b/bfd/elfnn-riscv.c
>> > @@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
>> >               max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
>> >               htab->max_alignment_for_gp = max_alignment;
>> >             }
>> > +         /* If the symbol is in the abs section, relaxation could
>> cause the gp
>> > +          * to move such that the gp relocation is no longer possible.
>>
>> I'm not quite sure what you mean by GP moving -- GP's the register, so
>> it doesn't have a value until runtime.  GP is meant to equal
>> __global_pointer$, but that's usually a data symbol and thus doesn't
>> move as a result of relaxation.
>>
>> We do have some other issues related to SHN_ABS (for example position
>> independent vs PC relative stuff), so it's possible there's some other
>> bug here?
>>
>> > +          * Conservatively half the allowed distance, as it cannot be
>> that
>> > +          * gp moves more than this, i.e. more than half the
>> instructions be
>> > +          * deleted due to relaxation.  Do this by adjusting
>> reserve_size.  */
>> > +         if (sym_sec->output_section == bfd_abs_section_ptr)
>> > +           {
>> > +             if (symval >= gp)
>> > +               reserve_size += (symval - gp) / 2;
>> > +             else
>> > +               reserve_size += (gp - symval) / 2;
>>
>> We can have more than a factor of two from relaxation, for example from
>> alignment.  If a hueristic is all we can do then I guess we'll have to
>> live with it, but I think I'd want to understand the movement
>>
>
> An extreme case is that all the instruction can be relaxed without any
> huge alignments between text and data, so I guess that's probably why the
> half of distance comes from.  If the default linker script may cause the
> problem, then we will need to know more details and try to resolve it.  But
> if this only occurs without the default linker script, then I will suggest
> users disable that relax patterns by the .norelax directive, or related
> options of compiler/assembler/linker.  Or maybe we can have an option for
> users to reject gp relax when meeting abs symbols, if without using default
> linker script.  However, please give a reduced case by using default linker
> script that will be broken in detailed, thanks a lot.
>
> Nelson
>
>
>> > +           }
>> >         }
>> >      }
>> >
>> > diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> > new file mode 100644
>> > index 00000000000..a018bb3a50a
>> > --- /dev/null
>> > +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> > @@ -0,0 +1,3 @@
>> > +.section .data
>> > +.globl sym
>> > +.set sym,0x10804
>> > diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> > new file mode 100644
>> > index 00000000000..2c7ab3a2579
>> > --- /dev/null
>> > +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> > @@ -0,0 +1,14 @@
>> > +#source: gp-relax-abs.s
>> > +#source: gp-relax-abs-sym.s
>> > +#as: -march=rv64ic -mabi=lp64
>> > +#ld: -Tcode-model-01.ld -melf64lriscv
>> > +#objdump: -d
>> > +
>> > +.*:[   ]+file format .*
>> > +
>> > +Disassembly of section \.text:
>> > +
>> > +[0-9a-f]+ <_start>:
>> > +.*auipc.*
>> > +.*lw.*# [0-9a-f]* <sym>
>> > +#pass
>> > diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> > new file mode 100644
>> > index 00000000000..db2103bafd1
>> > --- /dev/null
>> > +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> > @@ -0,0 +1,5 @@
>> > +.text
>> > +.global _start
>> > +_start:
>> > +    auipc t0, %pcrel_hi(sym)
>> > +    lw t0, %pcrel_lo(_start)(t0)
>> > diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> > index 947a266ba72..a53a2758991 100644
>> > --- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> > +++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> > @@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
>> >      run_dump_test "attr-merge-priv-spec-failed-06"
>> >      run_dump_test "attr-phdr"
>> >      run_dump_test "relax-max-align-gp"
>> > +    run_dump_test "gp-relax-abs"
>> >      run_dump_test "uleb128"
>> >      run_ld_link_tests [list \
>> >         [list "Weak reference 32" "-T weakref.ld
>> -m[riscv_choose_ilp32_emul]" "" \
>>
>

RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Joseph Faulls]

[-- Attachment #1: Type: text/plain, Size: 7833 bytes --]

Thanks for the replies!


  *   Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?
Yes, you can re-produce this with the default linkerscript, but it’s a little harder. If you take the same assembly files as the test cases in this patch (gp-relax-abs-sym.s and gp-relax-abs.s), assemble and link an elf and see the value __global_pointer$. Then adjust the absolute symbol to be this + 0x800. Re-assemble + link, and you should see a truncation.

I came across this issue when using a custom linker script that provided some symbols (which are absolute) and linking a program with quite a few relaxations.


  *   I'm not quite sure what you mean by GP moving -- GP's the register, so it doesn't have a value until runtime.  GP is meant to equal __global_pointer$, but that's usually a data symbol and thus doesn't move as a result of relaxation.
Perhaps I’m using the terms incorrectly, but if the __global_pointer is set in the linkerscript at the end of some section (I think this is most cases), then this value will change if the size of any section before it changes, as would be in the case of relaxation. Could we not describe this as the GP moving?

From: Nelson Chu <nelson@rivosinc.com>
Sent: Friday, July 28, 2023 2:16 AM
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Joseph Faulls <Joseph.Faulls@imgtec.com>; binutils@sourceware.org
Subject: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

Maybe, if the shrink code is more than the data segment alignment in the default linker script (0x1000), then probably still have a chance to get the truncated gp by using default linker script...  I will suggest if that is so, then we just have a linker option to disallow/allow the gp relax for any abs symbol, that should be more intuitive.

On Fri, Jul 28, 2023 at 9:02 AM Nelson Chu <nelson@rivosinc.com<mailto:nelson@rivosinc.com>> wrote:
Relaxation should shrink the text, but since the default linker script has huge data segment alignment, data after the segment alignment shouldn't be affected and shrinked, so ideally  it should be safe by using default linker script.

Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?

On Fri, Jul 28, 2023 at 5:08 AM Palmer Dabbelt <palmer@rivosinc.com<mailto:palmer@rivosinc.com>> wrote:
On Thu, 27 Jul 2023 09:48:24 PDT (-0700), Joseph.Faulls@imgtec.com<mailto:Joseph.Faulls@imgtec.com> wrote:
> Relaxations can cause the gp to move after it has been decided to gp
> relax. Against an absolute symbol, the distance may change such that the
> offset can no longer fit in the 12-bit immediate field.
>
> bfd/
>         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against and ABS
>           symbol if it is far away.
> ld/
>         * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
>         * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
> ---
> bfd/elfnn-riscv.c                            | 12 ++++++++++++
> ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
> ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
> ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
> ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
> 5 files changed, 35 insertions(+)
> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>
> diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c
> index 09aa7be225e..79e29e8b272 100644
> --- a/bfd/elfnn-riscv.c
> +++ b/bfd/elfnn-riscv.c
> @@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
>               max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
>               htab->max_alignment_for_gp = max_alignment;
>             }
> +         /* If the symbol is in the abs section, relaxation could cause the gp
> +          * to move such that the gp relocation is no longer possible.

I'm not quite sure what you mean by GP moving -- GP's the register, so
it doesn't have a value until runtime.  GP is meant to equal
__global_pointer$, but that's usually a data symbol and thus doesn't
move as a result of relaxation.

We do have some other issues related to SHN_ABS (for example position
independent vs PC relative stuff), so it's possible there's some other
bug here?

> +          * Conservatively half the allowed distance, as it cannot be that
> +          * gp moves more than this, i.e. more than half the instructions be
> +          * deleted due to relaxation.  Do this by adjusting reserve_size.  */
> +         if (sym_sec->output_section == bfd_abs_section_ptr)
> +           {
> +             if (symval >= gp)
> +               reserve_size += (symval - gp) / 2;
> +             else
> +               reserve_size += (gp - symval) / 2;

We can have more than a factor of two from relaxation, for example from
alignment.  If a hueristic is all we can do then I guess we'll have to
live with it, but I think I'd want to understand the movement

An extreme case is that all the instruction can be relaxed without any huge alignments between text and data, so I guess that's probably why the half of distance comes from.  If the default linker script may cause the problem, then we will need to know more details and try to resolve it.  But if this only occurs without the default linker script, then I will suggest users disable that relax patterns by the .norelax directive, or related options of compiler/assembler/linker.  Or maybe we can have an option for users to reject gp relax when meeting abs symbols, if without using default linker script.  However, please give a reduced case by using default linker script that will be broken in detailed, thanks a lot.

Nelson

> +           }
>         }
>      }
>
> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> new file mode 100644
> index 00000000000..a018bb3a50a
> --- /dev/null
> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
> @@ -0,0 +1,3 @@
> +.section .data
> +.globl sym
> +.set sym,0x10804
> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> new file mode 100644
> index 00000000000..2c7ab3a2579
> --- /dev/null
> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
> @@ -0,0 +1,14 @@
> +#source: gp-relax-abs.s
> +#source: gp-relax-abs-sym.s
> +#as: -march=rv64ic -mabi=lp64
> +#ld: -Tcode-model-01.ld -melf64lriscv
> +#objdump: -d
> +
> +.*:[   ]+file format .*
> +
> +Disassembly of section \.text:
> +
> +[0-9a-f]+ <_start>:
> +.*auipc.*
> +.*lw.*# [0-9a-f]* <sym>
> +#pass
> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> new file mode 100644
> index 00000000000..db2103bafd1
> --- /dev/null
> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
> @@ -0,0 +1,5 @@
> +.text
> +.global _start
> +_start:
> +    auipc t0, %pcrel_hi(sym)
> +    lw t0, %pcrel_lo(_start)(t0)
> diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> index 947a266ba72..a53a2758991 100644
> --- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> +++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
> @@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
>      run_dump_test "attr-merge-priv-spec-failed-06"
>      run_dump_test "attr-phdr"
>      run_dump_test "relax-max-align-gp"
> +    run_dump_test "gp-relax-abs"
>      run_dump_test "uleb128"
>      run_ld_link_tests [list \
>         [list "Weak reference 32" "-T weakref.ld -m[riscv_choose_ilp32_emul]" "" \

RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Palmer Dabbelt]

On Fri, 28 Jul 2023 02:18:49 PDT (-0700), Joseph.Faulls@imgtec.com wrote:
> Thanks for the replies!
> 
> 
>   *   Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?
> Yes, you can re-produce this with the default linkerscript, but it’s a little harder. If you take the same assembly files as the test cases in this patch (gp-relax-abs-sym.s and gp-relax-abs.s), assemble and link an elf and see the value __global_pointer$. Then adjust the absolute symbol to be this + 0x800. Re-assemble + link, and you should see a truncation.
> 
> I came across this issue when using a custom linker script that provided some symbols (which are absolute) and linking a program with quite a few relaxations.
> 
>   *   I'm not quite sure what you mean by GP moving -- GP's the register, so it doesn't have a value until runtime.  GP is meant to equal __global_pointer$, but that's usually a data symbol and thus doesn't move as a result of relaxation.
> Perhaps I’m using the terms incorrectly, but if the __global_pointer is set in the linkerscript at the end of some section (I think this is most cases), then this value will change if the size of any section before it changes, as would be in the case of relaxation. Could we not describe this as the GP moving?

I wouldn't, but I think it's just different meanings of the words here 
-- it shouldn't really matter for the purposes of fixing the bug, I 
think I understand what you're saying ;)

I think Nelson's point about cross-section GP relaxation is probably the 
root cause here, we've had some other bugs like that crop up recently.  
Assuming that's the case then SHN_ABS is just a red herring: maybe it 
makes triggering the bug easier, but we can probably come up with a 
similar failure in other ways.

Assuming that's the case, both SHN_ABS and /2 are just a hueristic here.  
We've got some tricky cases floating around for the cross-section stuff 
where we don't have a great answer yet, I wouldn't be surprised if this 
is another case where we just can't relax safely.

Can you post a reduced test case with a custom linker script that 
triggers the problem?  That should help us a bit more concrete.

> From: Nelson Chu <nelson@rivosinc.com>
> Sent: Friday, July 28, 2023 2:16 AM
> To: Palmer Dabbelt <palmer@rivosinc.com>
> Cc: Joseph Faulls <Joseph.Faulls@imgtec.com>; binutils@sourceware.org
> Subject: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.
> 
> Maybe, if the shrink code is more than the data segment alignment in the default linker script (0x1000), then probably still have a chance to get the truncated gp by using default linker script...  I will suggest if that is so, then we just have a linker option to disallow/allow the gp relax for any abs symbol, that should be more intuitive.
> 
> On Fri, Jul 28, 2023 at 9:02 AM Nelson Chu <nelson@rivosinc.com<mailto:nelson@rivosinc.com>> wrote:
> Relaxation should shrink the text, but since the default linker script has huge data segment alignment, data after the segment alignment shouldn't be affected and shrinked, so ideally  it should be safe by using default linker script.
> 
> Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?
> 
> On Fri, Jul 28, 2023 at 5:08 AM Palmer Dabbelt <palmer@rivosinc.com<mailto:palmer@rivosinc.com>> wrote:
> On Thu, 27 Jul 2023 09:48:24 PDT (-0700), Joseph.Faulls@imgtec.com<mailto:Joseph.Faulls@imgtec.com> wrote:
>> Relaxations can cause the gp to move after it has been decided to gp
>> relax. Against an absolute symbol, the distance may change such that the
>> offset can no longer fit in the 12-bit immediate field.
>>
>> bfd/
>>         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against and ABS
>>           symbol if it is far away.
>> ld/
>>         * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
>>         * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
>> ---
>> bfd/elfnn-riscv.c                            | 12 ++++++++++++
>> ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
>> ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
>> ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
>> ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
>> 5 files changed, 35 insertions(+)
>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>>
>> diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c
>> index 09aa7be225e..79e29e8b272 100644
>> --- a/bfd/elfnn-riscv.c
>> +++ b/bfd/elfnn-riscv.c
>> @@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
>>               max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
>>               htab->max_alignment_for_gp = max_alignment;
>>             }
>> +         /* If the symbol is in the abs section, relaxation could cause the gp
>> +          * to move such that the gp relocation is no longer possible.
> 
> I'm not quite sure what you mean by GP moving -- GP's the register, so
> it doesn't have a value until runtime.  GP is meant to equal
> __global_pointer$, but that's usually a data symbol and thus doesn't
> move as a result of relaxation.
> 
> We do have some other issues related to SHN_ABS (for example position
> independent vs PC relative stuff), so it's possible there's some other
> bug here?
> 
>> +          * Conservatively half the allowed distance, as it cannot be that
>> +          * gp moves more than this, i.e. more than half the instructions be
>> +          * deleted due to relaxation.  Do this by adjusting reserve_size.  */
>> +         if (sym_sec->output_section == bfd_abs_section_ptr)
>> +           {
>> +             if (symval >= gp)
>> +               reserve_size += (symval - gp) / 2;
>> +             else
>> +               reserve_size += (gp - symval) / 2;
> 
> We can have more than a factor of two from relaxation, for example from
> alignment.  If a hueristic is all we can do then I guess we'll have to
> live with it, but I think I'd want to understand the movement
> 
> An extreme case is that all the instruction can be relaxed without any huge alignments between text and data, so I guess that's probably why the half of distance comes from.  If the default linker script may cause the problem, then we will need to know more details and try to resolve it.  But if this only occurs without the default linker script, then I will suggest users disable that relax patterns by the .norelax directive, or related options of compiler/assembler/linker.  Or maybe we can have an option for users to reject gp relax when meeting abs symbols, if without using default linker script.  However, please give a reduced case by using default linker script that will be broken in detailed, thanks a lot.
> 
> Nelson
> 
>> +           }
>>         }
>>      }
>>
>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> new file mode 100644
>> index 00000000000..a018bb3a50a
>> --- /dev/null
>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> @@ -0,0 +1,3 @@
>> +.section .data
>> +.globl sym
>> +.set sym,0x10804
>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> new file mode 100644
>> index 00000000000..2c7ab3a2579
>> --- /dev/null
>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> @@ -0,0 +1,14 @@
>> +#source: gp-relax-abs.s
>> +#source: gp-relax-abs-sym.s
>> +#as: -march=rv64ic -mabi=lp64
>> +#ld: -Tcode-model-01.ld -melf64lriscv
>> +#objdump: -d
>> +
>> +.*:[   ]+file format .*
>> +
>> +Disassembly of section \.text:
>> +
>> +[0-9a-f]+ <_start>:
>> +.*auipc.*
>> +.*lw.*# [0-9a-f]* <sym>
>> +#pass
>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> new file mode 100644
>> index 00000000000..db2103bafd1
>> --- /dev/null
>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> @@ -0,0 +1,5 @@
>> +.text
>> +.global _start
>> +_start:
>> +    auipc t0, %pcrel_hi(sym)
>> +    lw t0, %pcrel_lo(_start)(t0)
>> diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> index 947a266ba72..a53a2758991 100644
>> --- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> +++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> @@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
>>      run_dump_test "attr-merge-priv-spec-failed-06"
>>      run_dump_test "attr-phdr"
>>      run_dump_test "relax-max-align-gp"
>> +    run_dump_test "gp-relax-abs"
>>      run_dump_test "uleb128"
>>      run_ld_link_tests [list \
>>         [list "Weak reference 32" "-T weakref.ld -m[riscv_choose_ilp32_emul]" "" \

RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Joseph Faulls]

> I think Nelson's point about cross-section GP relaxation is probably the root cause here, we've had some other bugs like that crop up recently.  
Assuming that's the case then SHN_ABS is just a red herring: maybe it makes triggering the bug easier, but we can probably come up with a similar failure in other ways.

Ah, I think you're right. My thought process was that any data not in the ABS section would move position if the sections before it shrunk / changed size, so that the offset to the gp would remain the same as instructions were relaxed. But you could place sections at particular addresses, so this bug would reveal itself just the same. I was able to hit the truncation issue with a very contrived test case.

> Can you post a reduced test case with a custom linker script that triggers the problem?  That should help us a bit more concrete.

Sure, here's an example I managed to create. I'm sure there's a way to reduce it further, without the weird C things to prevent optimising the buffer away. (etiquette question: should I be attaching these or just pasting them?)

Command: riscv64-unknown-elf-gcc test.c -c -o test.o; riscv64-unknown-elf-ld -melf64lriscv test.o -o test.elf -Ttest.ld

test.c:
extern char __bss_end[];
static char data[0x800];

void _start() {
  *__bss_end = 1;
}

char foo(int i) {
  data[i+1] = 1;
  return data[i];
}

test.ld:
ENTRY(_start)
MEMORY
{
        ram (!rx) : ORIGIN = 0x800000000, LENGTH = 0x1000
}
SECTIONS {
        .text : {
                *(.text*)
        } >ram

        .data : {
                *(.data*)
        } >ram

        __global_pointer$ = .;

        .bss : {
                *(.bss*)
        } >ram
        PROVIDE(__bss_end = .);
}

-----Original Message-----
From: Palmer Dabbelt <palmer@rivosinc.com> 
Sent: Friday, July 28, 2023 4:03 PM
To: Joseph Faulls <Joseph.Faulls@imgtec.com>
Cc: nelson@rivosinc.com; binutils@sourceware.org
Subject: RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

*** CAUTION: This email originates from a source not known to Imagination Technologies. Think before you click a link or open an attachment ***

On Fri, 28 Jul 2023 02:18:49 PDT (-0700), Joseph.Faulls@imgtec.com wrote:
> Thanks for the replies!
> 
> 
>   *   Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?
> Yes, you can re-produce this with the default linkerscript, but it’s a little harder. If you take the same assembly files as the test cases in this patch (gp-relax-abs-sym.s and gp-relax-abs.s), assemble and link an elf and see the value __global_pointer$. Then adjust the absolute symbol to be this + 0x800. Re-assemble + link, and you should see a truncation.
> 
> I came across this issue when using a custom linker script that provided some symbols (which are absolute) and linking a program with quite a few relaxations.
> 
>   *   I'm not quite sure what you mean by GP moving -- GP's the register, so it doesn't have a value until runtime.  GP is meant to equal __global_pointer$, but that's usually a data symbol and thus doesn't move as a result of relaxation.
> Perhaps I’m using the terms incorrectly, but if the __global_pointer is set in the linkerscript at the end of some section (I think this is most cases), then this value will change if the size of any section before it changes, as would be in the case of relaxation. Could we not describe this as the GP moving?

I wouldn't, but I think it's just different meanings of the words here
-- it shouldn't really matter for the purposes of fixing the bug, I think I understand what you're saying ;)

I think Nelson's point about cross-section GP relaxation is probably the root cause here, we've had some other bugs like that crop up recently.  
Assuming that's the case then SHN_ABS is just a red herring: maybe it makes triggering the bug easier, but we can probably come up with a similar failure in other ways.

Assuming that's the case, both SHN_ABS and /2 are just a hueristic here.  
We've got some tricky cases floating around for the cross-section stuff where we don't have a great answer yet, I wouldn't be surprised if this is another case where we just can't relax safely.

Can you post a reduced test case with a custom linker script that triggers the problem?  That should help us a bit more concrete.

> From: Nelson Chu <nelson@rivosinc.com>
> Sent: Friday, July 28, 2023 2:16 AM
> To: Palmer Dabbelt <palmer@rivosinc.com>
> Cc: Joseph Faulls <Joseph.Faulls@imgtec.com>; binutils@sourceware.org
> Subject: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.
> 
> Maybe, if the shrink code is more than the data segment alignment in the default linker script (0x1000), then probably still have a chance to get the truncated gp by using default linker script...  I will suggest if that is so, then we just have a linker option to disallow/allow the gp relax for any abs symbol, that should be more intuitive.
> 
> On Fri, Jul 28, 2023 at 9:02 AM Nelson Chu <nelson@rivosinc.com<mailto:nelson@rivosinc.com>> wrote:
> Relaxation should shrink the text, but since the default linker script has huge data segment alignment, data after the segment alignment shouldn't be affected and shrinked, so ideally  it should be safe by using default linker script.
> 
> Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?
> 
> On Fri, Jul 28, 2023 at 5:08 AM Palmer Dabbelt <palmer@rivosinc.com<mailto:palmer@rivosinc.com>> wrote:
> On Thu, 27 Jul 2023 09:48:24 PDT (-0700), Joseph.Faulls@imgtec.com<mailto:Joseph.Faulls@imgtec.com> wrote:
>> Relaxations can cause the gp to move after it has been decided to gp 
>> relax. Against an absolute symbol, the distance may change such that 
>> the offset can no longer fit in the 12-bit immediate field.
>>
>> bfd/
>>         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against and ABS
>>           symbol if it is far away.
>> ld/
>>         * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
>>         * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
>> ---
>> bfd/elfnn-riscv.c                            | 12 ++++++++++++
>> ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
>> ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
>> ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
>> ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
>> 5 files changed, 35 insertions(+)
>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>>
>> diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c index 
>> 09aa7be225e..79e29e8b272 100644
>> --- a/bfd/elfnn-riscv.c
>> +++ b/bfd/elfnn-riscv.c
>> @@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
>>               max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
>>               htab->max_alignment_for_gp = max_alignment;
>>             }
>> +         /* If the symbol is in the abs section, relaxation could cause the gp
>> +          * to move such that the gp relocation is no longer possible.
> 
> I'm not quite sure what you mean by GP moving -- GP's the register, so 
> it doesn't have a value until runtime.  GP is meant to equal 
> __global_pointer$, but that's usually a data symbol and thus doesn't 
> move as a result of relaxation.
> 
> We do have some other issues related to SHN_ABS (for example position 
> independent vs PC relative stuff), so it's possible there's some other 
> bug here?
> 
>> +          * Conservatively half the allowed distance, as it cannot be that
>> +          * gp moves more than this, i.e. more than half the instructions be
>> +          * deleted due to relaxation.  Do this by adjusting reserve_size.  */
>> +         if (sym_sec->output_section == bfd_abs_section_ptr)
>> +           {
>> +             if (symval >= gp)
>> +               reserve_size += (symval - gp) / 2;
>> +             else
>> +               reserve_size += (gp - symval) / 2;
> 
> We can have more than a factor of two from relaxation, for example 
> from alignment.  If a hueristic is all we can do then I guess we'll 
> have to live with it, but I think I'd want to understand the movement
> 
> An extreme case is that all the instruction can be relaxed without any huge alignments between text and data, so I guess that's probably why the half of distance comes from.  If the default linker script may cause the problem, then we will need to know more details and try to resolve it.  But if this only occurs without the default linker script, then I will suggest users disable that relax patterns by the .norelax directive, or related options of compiler/assembler/linker.  Or maybe we can have an option for users to reject gp relax when meeting abs symbols, if without using default linker script.  However, please give a reduced case by using default linker script that will be broken in detailed, thanks a lot.
> 
> Nelson
> 
>> +           }
>>         }
>>      }
>>
>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s 
>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> new file mode 100644
>> index 00000000000..a018bb3a50a
>> --- /dev/null
>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>> @@ -0,0 +1,3 @@
>> +.section .data
>> +.globl sym
>> +.set sym,0x10804
>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d 
>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> new file mode 100644
>> index 00000000000..2c7ab3a2579
>> --- /dev/null
>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>> @@ -0,0 +1,14 @@
>> +#source: gp-relax-abs.s
>> +#source: gp-relax-abs-sym.s
>> +#as: -march=rv64ic -mabi=lp64
>> +#ld: -Tcode-model-01.ld -melf64lriscv
>> +#objdump: -d
>> +
>> +.*:[   ]+file format .*
>> +
>> +Disassembly of section \.text:
>> +
>> +[0-9a-f]+ <_start>:
>> +.*auipc.*
>> +.*lw.*# [0-9a-f]* <sym>
>> +#pass
>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s 
>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> new file mode 100644
>> index 00000000000..db2103bafd1
>> --- /dev/null
>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>> @@ -0,0 +1,5 @@
>> +.text
>> +.global _start
>> +_start:
>> +    auipc t0, %pcrel_hi(sym)
>> +    lw t0, %pcrel_lo(_start)(t0)
>> diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp 
>> b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> index 947a266ba72..a53a2758991 100644
>> --- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> +++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>> @@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
>>      run_dump_test "attr-merge-priv-spec-failed-06"
>>      run_dump_test "attr-phdr"
>>      run_dump_test "relax-max-align-gp"
>> +    run_dump_test "gp-relax-abs"
>>      run_dump_test "uleb128"
>>      run_ld_link_tests [list \
>>         [list "Weak reference 32" "-T weakref.ld 
>> -m[riscv_choose_ilp32_emul]" "" \

RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Palmer Dabbelt]

On Fri, 28 Jul 2023 08:52:41 PDT (-0700), Joseph.Faulls@imgtec.com wrote:
>> I think Nelson's point about cross-section GP relaxation is probably the root cause here, we've had some other bugs like that crop up recently.  
> Assuming that's the case then SHN_ABS is just a red herring: maybe it makes triggering the bug easier, but we can probably come up with a similar failure in other ways.
> 
> Ah, I think you're right. My thought process was that any data not in the ABS section would move position if the sections before it shrunk / changed size, so that the offset to the gp would remain the same as instructions were relaxed. But you could place sections at particular addresses, so this bug would reveal itself just the same. I was able to hit the truncation issue with a very contrived test case.

Yep, these test cases always end up pretty contrived because you're 
trying to reliably get symbols at specific offsets to trigger the bug.  
I don't think there's really any way around it.

>> Can you post a reduced test case with a custom linker script that triggers the problem?  That should help us a bit more concrete.
> 
> Sure, here's an example I managed to create. I'm sure there's a way to reduce it further, without the weird C things to prevent optimising the buffer away. (etiquette question: should I be attaching these or just pasting them?)

I don't think it really matters, we just need something concrete so 
we're all talking about the same thing.  At some point it'll end up in 
there as a real test case with all the DG bits, until then it's just 
going to be us talking through things.

> Command: riscv64-unknown-elf-gcc test.c -c -o test.o; riscv64-unknown-elf-ld -melf64lriscv test.o -o test.elf -Ttest.ld
> 
> test.c:
> extern char __bss_end[];
> static char data[0x800];
> 
> void _start() {
>   *__bss_end = 1;
> }
> 
> char foo(int i) {
>   data[i+1] = 1;
>   return data[i];
> }

FWIW, it can frequently be easier to expose these sorts of things by 
just writing assembly instead of trying to get the compiler to do it -- 
that way you don't need to worry about nonsensical C code getting 
optimized away.  I frequently just grab the output of the compiler for a 
case that looks similar and then massage the assembly to get things to 
break.

> test.ld:
> ENTRY(_start)
> MEMORY
> {
>         ram (!rx) : ORIGIN = 0x800000000, LENGTH = 0x1000
> }
> SECTIONS {
>         .text : {
>                 *(.text*)
>         } >ram
> 
>         .data : {
>                 *(.data*)
>         } >ram
> 
>         __global_pointer$ = .;

So I think that's it: .text shrinks so .data moves, and goes out of 
range of __global_pointer$.  We could probaby get similar breakages if 
__global_pointer$ is in any section that doesn't end up in the same 
segment as .data (or any symbol referenced via GP), and also from some 
of the alignment-related stuff like we recently ran into.

> 
>         .bss : {
>                 *(.bss*)
>         } >ram
>         PROVIDE(__bss_end = .);
> }

IIRC Nelson has already started looking into some of the alignment-based 
cross-section relaxation issues.  Probably best to let him chime in, 
it's the weekend in Taiwan already so that might just be next week.

Given that we've found two bugs here in the last few months we've 
probably got a few more floating around, so it's probably worth thinking 
through this a bit more.  That might take a little while, but sounds 
like it's worth doing.

Obviously happy to see a patch that fixes it if you feel like hacking on 
this stuff a bit ;)

> 
> -----Original Message-----
> From: Palmer Dabbelt <palmer@rivosinc.com> 
> Sent: Friday, July 28, 2023 4:03 PM
> To: Joseph Faulls <Joseph.Faulls@imgtec.com>
> Cc: nelson@rivosinc.com; binutils@sourceware.org
> Subject: RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.
> 
> *** CAUTION: This email originates from a source not known to Imagination Technologies. Think before you click a link or open an attachment ***
> 
> On Fri, 28 Jul 2023 02:18:49 PDT (-0700), Joseph.Faulls@imgtec.com wrote:
>> Thanks for the replies!
>> 
>> 
>>   *   Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?
>> Yes, you can re-produce this with the default linkerscript, but it’s a little harder. If you take the same assembly files as the test cases in this patch (gp-relax-abs-sym.s and gp-relax-abs.s), assemble and link an elf and see the value __global_pointer$. Then adjust the absolute symbol to be this + 0x800. Re-assemble + link, and you should see a truncation.
>> 
>> I came across this issue when using a custom linker script that provided some symbols (which are absolute) and linking a program with quite a few relaxations.
>> 
>>   *   I'm not quite sure what you mean by GP moving -- GP's the register, so it doesn't have a value until runtime.  GP is meant to equal __global_pointer$, but that's usually a data symbol and thus doesn't move as a result of relaxation.
>> Perhaps I’m using the terms incorrectly, but if the __global_pointer is set in the linkerscript at the end of some section (I think this is most cases), then this value will change if the size of any section before it changes, as would be in the case of relaxation. Could we not describe this as the GP moving?
> 
> I wouldn't, but I think it's just different meanings of the words here
> -- it shouldn't really matter for the purposes of fixing the bug, I think I understand what you're saying ;)
> 
> I think Nelson's point about cross-section GP relaxation is probably the root cause here, we've had some other bugs like that crop up recently.  
> Assuming that's the case then SHN_ABS is just a red herring: maybe it makes triggering the bug easier, but we can probably come up with a similar failure in other ways.
> 
> Assuming that's the case, both SHN_ABS and /2 are just a hueristic here.  
> We've got some tricky cases floating around for the cross-section stuff where we don't have a great answer yet, I wouldn't be surprised if this is another case where we just can't relax safely.
> 
> Can you post a reduced test case with a custom linker script that triggers the problem?  That should help us a bit more concrete.
> 
>> From: Nelson Chu <nelson@rivosinc.com>
>> Sent: Friday, July 28, 2023 2:16 AM
>> To: Palmer Dabbelt <palmer@rivosinc.com>
>> Cc: Joseph Faulls <Joseph.Faulls@imgtec.com>; binutils@sourceware.org
>> Subject: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.
>> 
>> Maybe, if the shrink code is more than the data segment alignment in the default linker script (0x1000), then probably still have a chance to get the truncated gp by using default linker script...  I will suggest if that is so, then we just have a linker option to disallow/allow the gp relax for any abs symbol, that should be more intuitive.
>> 
>> On Fri, Jul 28, 2023 at 9:02 AM Nelson Chu <nelson@rivosinc.com<mailto:nelson@rivosinc.com>> wrote:
>> Relaxation should shrink the text, but since the default linker script has huge data segment alignment, data after the segment alignment shouldn't be affected and shrinked, so ideally  it should be safe by using default linker script.
>> 
>> Do you have a reduced test that shows we still have a chance to get the relax error by using the default linker script?
>> 
>> On Fri, Jul 28, 2023 at 5:08 AM Palmer Dabbelt <palmer@rivosinc.com<mailto:palmer@rivosinc.com>> wrote:
>> On Thu, 27 Jul 2023 09:48:24 PDT (-0700), Joseph.Faulls@imgtec.com<mailto:Joseph.Faulls@imgtec.com> wrote:
>>> Relaxations can cause the gp to move after it has been decided to gp 
>>> relax. Against an absolute symbol, the distance may change such that 
>>> the offset can no longer fit in the 12-bit immediate field.
>>>
>>> bfd/
>>>         * elfnn-riscv.c (_bfd_riscv_relax_pc) Do not gp relax against and ABS
>>>           symbol if it is far away.
>>> ld/
>>>         * ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp: Updated.
>>>         * ld/testsuite/ld-riscv-elf/gp-relax-abs*: New testcases.
>>> ---
>>> bfd/elfnn-riscv.c                            | 12 ++++++++++++
>>> ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s |  3 +++
>>> ld/testsuite/ld-riscv-elf/gp-relax-abs.d     | 14 ++++++++++++++
>>> ld/testsuite/ld-riscv-elf/gp-relax-abs.s     |  5 +++++
>>> ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp   |  1 +
>>> 5 files changed, 35 insertions(+)
>>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>>> create mode 100644 ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>>>
>>> diff --git a/bfd/elfnn-riscv.c b/bfd/elfnn-riscv.c index 
>>> 09aa7be225e..79e29e8b272 100644
>>> --- a/bfd/elfnn-riscv.c
>>> +++ b/bfd/elfnn-riscv.c
>>> @@ -4885,6 +4885,18 @@ _bfd_riscv_relax_pc (bfd *abfd ATTRIBUTE_UNUSED,
>>>               max_alignment = _bfd_riscv_get_max_alignment (sec, gp);
>>>               htab->max_alignment_for_gp = max_alignment;
>>>             }
>>> +         /* If the symbol is in the abs section, relaxation could cause the gp
>>> +          * to move such that the gp relocation is no longer possible.
>> 
>> I'm not quite sure what you mean by GP moving -- GP's the register, so 
>> it doesn't have a value until runtime.  GP is meant to equal 
>> __global_pointer$, but that's usually a data symbol and thus doesn't 
>> move as a result of relaxation.
>> 
>> We do have some other issues related to SHN_ABS (for example position 
>> independent vs PC relative stuff), so it's possible there's some other 
>> bug here?
>> 
>>> +          * Conservatively half the allowed distance, as it cannot be that
>>> +          * gp moves more than this, i.e. more than half the instructions be
>>> +          * deleted due to relaxation.  Do this by adjusting reserve_size.  */
>>> +         if (sym_sec->output_section == bfd_abs_section_ptr)
>>> +           {
>>> +             if (symval >= gp)
>>> +               reserve_size += (symval - gp) / 2;
>>> +             else
>>> +               reserve_size += (gp - symval) / 2;
>> 
>> We can have more than a factor of two from relaxation, for example 
>> from alignment.  If a hueristic is all we can do then I guess we'll 
>> have to live with it, but I think I'd want to understand the movement
>> 
>> An extreme case is that all the instruction can be relaxed without any huge alignments between text and data, so I guess that's probably why the half of distance comes from.  If the default linker script may cause the problem, then we will need to know more details and try to resolve it.  But if this only occurs without the default linker script, then I will suggest users disable that relax patterns by the .norelax directive, or related options of compiler/assembler/linker.  Or maybe we can have an option for users to reject gp relax when meeting abs symbols, if without using default linker script.  However, please give a reduced case by using default linker script that will be broken in detailed, thanks a lot.
>> 
>> Nelson
>> 
>>> +           }
>>>         }
>>>      }
>>>
>>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s 
>>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>>> new file mode 100644
>>> index 00000000000..a018bb3a50a
>>> --- /dev/null
>>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs-sym.s
>>> @@ -0,0 +1,3 @@
>>> +.section .data
>>> +.globl sym
>>> +.set sym,0x10804
>>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.d 
>>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>>> new file mode 100644
>>> index 00000000000..2c7ab3a2579
>>> --- /dev/null
>>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.d
>>> @@ -0,0 +1,14 @@
>>> +#source: gp-relax-abs.s
>>> +#source: gp-relax-abs-sym.s
>>> +#as: -march=rv64ic -mabi=lp64
>>> +#ld: -Tcode-model-01.ld -melf64lriscv
>>> +#objdump: -d
>>> +
>>> +.*:[   ]+file format .*
>>> +
>>> +Disassembly of section \.text:
>>> +
>>> +[0-9a-f]+ <_start>:
>>> +.*auipc.*
>>> +.*lw.*# [0-9a-f]* <sym>
>>> +#pass
>>> diff --git a/ld/testsuite/ld-riscv-elf/gp-relax-abs.s 
>>> b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>>> new file mode 100644
>>> index 00000000000..db2103bafd1
>>> --- /dev/null
>>> +++ b/ld/testsuite/ld-riscv-elf/gp-relax-abs.s
>>> @@ -0,0 +1,5 @@
>>> +.text
>>> +.global _start
>>> +_start:
>>> +    auipc t0, %pcrel_hi(sym)
>>> +    lw t0, %pcrel_lo(_start)(t0)
>>> diff --git a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp 
>>> b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>>> index 947a266ba72..a53a2758991 100644
>>> --- a/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>>> +++ b/ld/testsuite/ld-riscv-elf/ld-riscv-elf.exp
>>> @@ -172,6 +172,7 @@ if [istarget "riscv*-*-*"] {
>>>      run_dump_test "attr-merge-priv-spec-failed-06"
>>>      run_dump_test "attr-phdr"
>>>      run_dump_test "relax-max-align-gp"
>>> +    run_dump_test "gp-relax-abs"
>>>      run_dump_test "uleb128"
>>>      run_ld_link_tests [list \
>>>         [list "Weak reference 32" "-T weakref.ld 
>>> -m[riscv_choose_ilp32_emul]" "" \

Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Maciej W. Rozycki]

On Thu, 27 Jul 2023, Joseph Faulls wrote:

> Relaxations can cause the gp to move after it has been decided to gp
> relax. Against an absolute symbol, the distance may change such that the
> offset can no longer fit in the 12-bit immediate field.

 What's the use case for using AUIPC/LW to load an absolute symbol?  Such 
symbols are not used in contexts where an address could alternatively be 
expected, so the correct sequence, and in PIC or PIE code indeed the only 
valid, for direct references from code is LUI/ADDI.  Since you're fiddling 
with linker relaxation code here, you may well take the opportunity and 
relax it to LUI/ADDI, or ADDI alone if the value is small.  There may be 
an issue with RV64 objects if the value turns out outside the 32-bit range 
though, which will be a relocation overflow.

  Maciej

RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Joseph Faulls]

> What's the use case for using AUIPC/LW to load an absolute symbol?  Such symbols are not used in contexts where an address could alternatively be expected, so the correct sequence, and in PIC or PIE code indeed the only valid, for direct references from code is LUI/ADDI

For my clarification, are you saying that the AUIPC/LW should never have been generated? If so, how is it possible for the compiler to know that the symbol referenced will be an absolute symbol?

Regardless, that's a good point, changing all AUIPC/LW to LUI/ADDI for absolute symbols makes sense to me. I could try and do this if it's good way forward, but I would like a second opinion first! Palmer, Nelson, what are your thoughts?

-----Original Message-----
From: Maciej W. Rozycki <macro@orcam.me.uk> 
Sent: Tuesday, August 8, 2023 10:49 AM
To: Joseph Faulls <Joseph.Faulls@imgtec.com>
Cc: binutils@sourceware.org; palmer@rivosinc.com; nelson@rivosinc.com
Subject: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

On Thu, 27 Jul 2023, Joseph Faulls wrote:

> Relaxations can cause the gp to move after it has been decided to gp 
> relax. Against an absolute symbol, the distance may change such that 
> the offset can no longer fit in the 12-bit immediate field.

 What's the use case for using AUIPC/LW to load an absolute symbol?  Such symbols are not used in contexts where an address could alternatively be expected, so the correct sequence, and in PIC or PIE code indeed the only valid, for direct references from code is LUI/ADDI.  Since you're fiddling with linker relaxation code here, you may well take the opportunity and relax it to LUI/ADDI, or ADDI alone if the value is small.  There may be an issue with RV64 objects if the value turns out outside the 32-bit range though, which will be a relocation overflow.

  Maciej

RE: [EXTERNAL] Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Maciej W. Rozycki]

On Tue, 8 Aug 2023, Joseph Faulls wrote:

> > What's the use case for using AUIPC/LW to load an absolute symbol?  
> > Such symbols are not used in contexts where an address could 
> > alternatively be expected, so the correct sequence, and in PIC or PIE 
> > code indeed the only valid, for direct references from code is 
> > LUI/ADDI
> 
> For my clarification, are you saying that the AUIPC/LW should never have 
> been generated? If so, how is it possible for the compiler to know that 
> the symbol referenced will be an absolute symbol?

 No, the compiler won't ever know that a reference will ultimately resolve 
to an absolute symbol; I don't think there's a way to tell it.  Then such 
symbols aren't usually used in compiled code as they are awkward to refer 
to (e.g. in C you'll only ever use `&symbol' to get at one).  Most often 
I'd expect them to be referred in handcoded assembly, via the LI macro, 
and possibly defined via the GAS's or LD's `--defsym' command-line option, 
or in a linker script.

  Maciej

Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

[Joseph Faulls]

Ping - is changing all AUIPC/LW to LUI/ADDI/LW for absolute symbols the best way forward?

-----Original Message-----
From: Joseph Faulls 
Sent: Tuesday, August 8, 2023 11:38 AM
To: Maciej W. Rozycki <macro@orcam.me.uk>
Cc: binutils@sourceware.org; palmer@rivosinc.com; nelson@rivosinc.com
Subject: Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

> What's the use case for using AUIPC/LW to load an absolute symbol?  
> Such symbols are not used in contexts where an address could 
> alternatively be expected, so the correct sequence, and in PIC or PIE 
> code indeed the only valid, for direct references from code is 
> LUI/ADDI

For my clarification, are you saying that the AUIPC/LW should never have been generated? If so, how is it possible for the compiler to know that the symbol referenced will be an absolute symbol?

Regardless, that's a good point, changing all AUIPC/LW to LUI/ADDI for absolute symbols makes sense to me. I could try and do this if it's good way forward, but I would like a second opinion first! Palmer, Nelson, what are your thoughts?

-----Original Message-----
From: Maciej W. Rozycki <macro@orcam.me.uk>
Sent: Tuesday, August 8, 2023 10:49 AM
To: Joseph Faulls <Joseph.Faulls@imgtec.com>
Cc: binutils@sourceware.org; palmer@rivosinc.com; nelson@rivosinc.com
Subject: Re: [PATCH] RISC-V: Do not gp relax against an ABS symbol if it is far away.

On Thu, 27 Jul 2023, Joseph Faulls wrote:

> Relaxations can cause the gp to move after it has been decided to gp 
> relax. Against an absolute symbol, the distance may change such that 
> the offset can no longer fit in the 12-bit immediate field.

 What's the use case for using AUIPC/LW to load an absolute symbol?  Such symbols are not used in contexts where an address could alternatively be expected, so the correct sequence, and in PIC or PIE code indeed the only valid, for direct references from code is LUI/ADDI.  Since you're fiddling with linker relaxation code here, you may well take the opportunity and relax it to LUI/ADDI, or ADDI alone if the value is small.  There may be an issue with RV64 objects if the value turns out outside the 32-bit range though, which will be a relocation overflow.

  Maciej