Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

-debug-only=jit emits unpleasent output #1612

Closed
lattner opened this issue Mar 4, 2007 · 5 comments
Closed

-debug-only=jit emits unpleasent output #1612

lattner opened this issue Mar 4, 2007 · 5 comments
Labels
bugzilla Issues migrated from bugzilla mcjit

Comments

@lattner
Copy link
Collaborator

lattner commented Mar 4, 2007

Bugzilla Link 1240
Resolution FIXED
Resolved on Feb 22, 2010 12:43
Version 1.0
OS MacOS X
CC @asl

Extended Description

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
@asl
Copy link
Collaborator

asl commented Mar 5, 2007

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?

@asl
Copy link
Collaborator

asl commented Mar 5, 2007

s/should/shouldn't

@lattner
Copy link
Collaborator Author

lattner commented Mar 6, 2007

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

@asl
Copy link
Collaborator

asl commented Mar 6, 2007

Fixed with

http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070305/045594.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070305/045595.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070305/045596.html

@llvmbot
Copy link
Collaborator

llvmbot commented Nov 26, 2021

mentioned in issue llvm/llvm-bugzilla-archive#26879

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
troelsbjerre pushed a commit to troelsbjerre/llvm-project that referenced this issue Jan 10, 2024
@fredriss
Merge pull request llvm#1612 from JDevlieghere/🍒/86aa8e6363c7e00f211d…
90ad9e7 
…e62ccb3236556e9841df

[lldb] Use target.GetLaunchInfo() instead of creating an empty one.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla mcjit
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@asl @lattner @llvmbot