On Tue, Dec 01, 2020 at 01:48:31PM +0100, Jakub Jelinek via Gcc-patches wrote:
> I guess it depends on whether for 32-bit target and -gdwarf64, when
> calling dw2_assemble_integer with non-CONST_INT argument we only
> need positive values or might need negative ones too.
> Because positive ones can
On Tue, Dec 01, 2020 at 01:03:07PM +0100, Richard Biener wrote:
> > So yes, we can either do a sorry, error, or could just avoid 64-bit
> > relocations (depending on endianity instead of emitting
> > .quad expression_that_needs_relocation
> > emit
> > .long expression_that_needs_relocation, 0
> > o
On Tue, 1 Dec 2020, Jakub Jelinek wrote:
> On Tue, Dec 01, 2020 at 11:49:43AM +0100, Richard Biener wrote:
> > On Tue, 1 Dec 2020, Jakub Jelinek wrote:
> >
> > > Hi!
> > >
> > > The following patch makes the choice between 32-bit and 64-bit DWARF
> > > formats
> > > selectable by command line s
On Tue, Dec 01, 2020 at 11:49:43AM +0100, Richard Biener wrote:
> On Tue, 1 Dec 2020, Jakub Jelinek wrote:
>
> > Hi!
> >
> > The following patch makes the choice between 32-bit and 64-bit DWARF formats
> > selectable by command line switch, rather than being hardcoded through
> > DWARF_OFFSET_SIZ
On Tue, 1 Dec 2020, Jakub Jelinek wrote:
> Hi!
>
> The following patch makes the choice between 32-bit and 64-bit DWARF formats
> selectable by command line switch, rather than being hardcoded through
> DWARF_OFFSET_SIZE macro.
>
> The options themselves don't turn on debug info themselves, so o
Hi!
The following patch makes the choice between 32-bit and 64-bit DWARF formats
selectable by command line switch, rather than being hardcoded through
DWARF_OFFSET_SIZE macro.
The options themselves don't turn on debug info themselves, so one needs
to use -g -gdwarf64 or similar.
Ok for trunk i
