On Tue, 11 Jul 2023, Florian Weimer via Gcc wrote:
> * Richard Biener:
>
> > On Tue, Jul 11, 2023 at 11:36 AM Florian Weimer via Gcc
> > wrote:
> >>
> >> How does the Coldfire m68k subtarget and sure that displacements in PIC
> >> code are within the addressable range?
> >
> > There is usually
On 7/11/23 04:48, Richard Biener via Gcc wrote:
On Tue, Jul 11, 2023 at 11:36 AM Florian Weimer via Gcc wrote:
How does the Coldfire m68k subtarget and sure that displacements in PIC
code are within the addressable range?
There is usually a branch shortening pass relying on correct
instru
* Richard Biener:
> On Tue, Jul 11, 2023 at 11:36 AM Florian Weimer via Gcc
> wrote:
>>
>> How does the Coldfire m68k subtarget and sure that displacements in PIC
>> code are within the addressable range?
>
> There is usually a branch shortening pass relying on correct
> instruction lengths.
>
>
On Tue, Jul 11, 2023 at 11:36 AM Florian Weimer via Gcc wrote:
>
> How does the Coldfire m68k subtarget and sure that displacements in PIC
> code are within the addressable range?
There is usually a branch shortening pass relying on correct
instruction lengths.
I suggest to file a bugreport with
How does the Coldfire m68k subtarget and sure that displacements in PIC
code are within the addressable range?
We have a source file in glibc that fails at assembly because it
contains a branch that is out of range with -fpic. The GAS error is:
…/iso-2022-jp.s: Fatal error: Tried to convert PC r
