https://sourceware.org/bugzilla/show_bug.cgi?id=28867
--- Comment #2 from Eric Pouech ---
Created attachment 14015
--> https://sourceware.org/bugzilla/attachment.cgi?id=14015&action=edit
fail.s file
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=28867
--- Comment #3 from Eric Pouech ---
Created attachment 14016
--> https://sourceware.org/bugzilla/attachment.cgi?id=14016&action=edit
fail.o file
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=28867
--- Comment #4 from Eric Pouech ---
Created attachment 14017
--> https://sourceware.org/bugzilla/attachment.cgi?id=14017&action=edit
good.s file
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=28867
--- Comment #5 from Eric Pouech ---
Created attachment 14018
--> https://sourceware.org/bugzilla/attachment.cgi?id=14018&action=edit
good.o file
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=28867
--- Comment #6 from Eric Pouech ---
command line for linking:
Note1: winegcc is Wine's gcc wrapper for generating the compilation/build
operations. Here it's use is for linking a DLL, we need to generate some PE
fields (like export table...).
https://sourceware.org/bugzilla/show_bug.cgi?id=28867
--- Comment #8 from Eric Pouech ---
Hi Nick,
I've tried it locally as well, but as you, without much success... ie no error
generated from re-assembling the fail.s file
the exact command line is:
/usr/lib/gcc/i686-w64-mingw32/11.2.1/../../.
https://sourceware.org/bugzilla/show_bug.cgi?id=28867
--- Comment #10 from Eric Pouech ---
> Not really. I think that we are looking at three possibilities here:
>
> * A bug in the compiler used to build the assembler that you
> are using, so that it mis-behaves in a subtle manner. Sin
Component: gas
Assignee: unassigned at sourceware dot org
Reporter: eric.pouech at orange dot fr
Target Milestone: ---
using this input:
<<<<<
.text
.globl func
func:
.cfi_startproc
ret
.cfi_endproc
<<<<
https://sourceware.org/bugzilla/show_bug.cgi?id=30853
--- Comment #2 from Eric Pouech ---
I see...
that's why I suppose gcc doesn't rely on (g)as' cfi directives to emit its
dwarf CFI bits
(unless there's an option to tell x86_64-w64-mingw32-as to pick up another
flavor, but couldn't find it eit
https://sourceware.org/bugzilla/show_bug.cgi?id=30853
--- Comment #3 from Eric Pouech ---
which COFF register numbering are you referring to?
and how are we supposed to generate CIE from .cfi directives that would match
dwarf debug information (for return address column)?
using ".cfi_startproc
: binutils
Assignee: unassigned at sourceware dot org
Reporter: eric.pouech at orange dot fr
Target Milestone: ---
Following report to gcc https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104399
after adding one letter to a string inside a .c program, compilation and link
fails
11 matches
Mail list logo
