On Sep 04 2023, Vincent Rivière wrote:
> By looking at the sections generated by m68k-elf-g++, I noticed there was
> relocations to odd addresses in the .eh_frame section. Is this expected?
> Is there a way to avoid that, maybe by adding some padding?
I think you need
Hi,
By looking at the sections generated by m68k-elf-g++, I noticed there
was relocations to odd addresses in the .eh_frame section. Is this
expected? Is there a way to avoid that, maybe by adding some padding?
Actually, I would like to upgrade the experimental m68k-atari-mintelf
toolchain
On 29 May 2007 15:27:43 -0700, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:
> I wonder why when I compile standard C programs using "gcc -v simple.c"
> I can see that the linker adds the "--eh-frame-hdr" parameter ?
That option is always used if the linker supports it.
> After all there is no us
"sfora dim" <[EMAIL PROTECTED]> writes:
> I read that the eh_frame is for exceptions support,
> for languages like C++ for instance.
Yes.
> I wonder why when I compile standard C programs using "gcc -v simple.c"
> I can see that the linker adds the "--eh-frame-hdr" parameter ?
That option is al
Hello,
I read that the eh_frame is for exceptions support,
for languages like C++ for instance.
I wonder why when I compile standard C programs using "gcc -v simple.c"
I can see that the linker adds the "--eh-frame-hdr" parameter ?
After all there is no use for the eh section when we don't supp
