LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 1240 - -debug-only=jit emits unpleasent output
Summary: -debug-only=jit emits unpleasent output
Status: RESOLVED FIXED
Alias: None
Product: libraries
Classification: Unclassified
Component: MCJIT (show other bugs)
Version: 1.0
Hardware: Macintosh MacOS X
: P normal
Assignee: Unassigned LLVM Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-04 00:37 PST by Chris Lattner
Modified: 2010-02-22 12:43 PST (History)
2 users (show)

See Also:
Fixed By Commit(s):

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Lattner 2007-03-04 00:37:41 PST 
I get stuff like:

JIT: Stub emitted at [0x7087fd8] for function 'test'
JIT: Finished CodeGen of [0x7088028] Function: main: 88 bytes of text, 9 relocations
Disassembled code:
No disassembler available. See configure help for avaiable options.
JIT: Lazily resolving function 'test' In stub ptr = 0x7087ff0 actual ptr = 0x7087fd8
JIT: Finished CodeGen of [0x7088090] Function: test: 12 bytes of text, 0 relocations
Disassembled code:
No disassembler available. See configure help for avaiable options.

It would be much better if the "Disassembled code/No disassembler available" lines just were not 
printed on targets without a disassembler.

-Chris
Comment 1 Anton Korobeynikov 2007-03-05 08:03:37 PST 
Currently we're supporting only udis86 library for x86-{32,64} code. So, I
assume, that this message should be printed in case of any other target. Right?
Comment 2 Anton Korobeynikov 2007-03-05 08:18:33 PST 
s/should/shouldn't
Comment 3 Chris Lattner 2007-03-05 17:17:03 PST 
Right.  I would suggest that libsystem export a "hasDisassembler()" function.  If this returns false, the JIT 
should not attempt to disassemble the produced code.

-chris