* Epilogue problems x86
@ 2003-09-18 6:14 Brian
2003-09-18 12:01 ` Eljay Love-Jensen
0 siblings, 1 reply; 2+ messages in thread
From: Brian @ 2003-09-18 6:14 UTC (permalink / raw)
To: gcc-help
I am trying to insert a label at the end of every function.
Then, I will use this label later when I parse the assembly to
insert a function call
Keep in mind that my approach requires the -S flag for C files.
Then I parse the asm and fix it up, and finally compile the asm file to
an executable or object file.
I search for the EPILOGE_END note using the following:
if(GET_CODE(insn_ptr) == NOTE)
{
if(strcmp("NOTE_INSN_EPILOGUE_BEG", GET_NOTE_INSN_NAME
(NOTE_LINE_NUMBER (insn_ptr))) == 0)
After I see this I use emit_label_before(pattern, insn_ptr)
(I have also tried emit_label_after, and several permutations thereof)
For small files everything is fine and dandy, but for large compiles
I inevitably get an internal error. For example:
samplein.c: In function `initAIFF':
samplein.c:595: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions.
Any ideas on why the compiler bombs here?
Brian
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Epilogue problems x86
2003-09-18 6:14 Epilogue problems x86 Brian
@ 2003-09-18 12:01 ` Eljay Love-Jensen
0 siblings, 0 replies; 2+ messages in thread
From: Eljay Love-Jensen @ 2003-09-18 12:01 UTC (permalink / raw)
To: bblietz, gcc-help
Hi Brian,
What's the bt in gdb say about core?
--Eljay
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-09-18 12:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-09-18 6:14 Epilogue problems x86 Brian
2003-09-18 12:01 ` Eljay Love-Jensen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).