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.

Sign up for GitHub

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

opt tool registers multiple command line options #1257

Closed
llvmbot opened this issue Aug 19, 2006 · 2 comments
Closed

opt tool registers multiple command line options #1257

llvmbot opened this issue Aug 19, 2006 · 2 comments
Assignees
@lattner
Labels
bugzilla Issues migrated from bugzilla regression

Comments

@llvmbot
Copy link
Member

llvmbot commented Aug 19, 2006

Bugzilla Link 885
Resolution FIXED
Resolved on Mar 06, 2010 14:00
Version trunk
OS All
Reporter LLVM Bugzilla Contributor

Extended Description

After the analyze functionality was merged into opt, it now seems to register
multiple command line options. The simple command:

opt < /dev/null

will reproduce this output:

: CommandLine Error: Argument 'printm' defined more than once!
: CommandLine Error: Argument 'profile-loader' defined more than once!
: CommandLine Error: Argument 'print' defined more than once!
opt: Standard Input empty!

Its not clear what's going on. Debugging this problem has lead to the errors
being generated in the bowels of the PassNameParser that is used to collect all
the analysis passes. However, its unclear how this could lead to duplicate pass
registrations.

Perhaps someone with a better handle on this code can figure it out.
@llvmbot
Copy link
Member Author

llvmbot commented Aug 19, 2006

assigned to @lattner

@lattner
Copy link
Collaborator

lattner commented Aug 21, 2006

Fixed:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060821/036910.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060821/036911.html

-Chris

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
xlauko pushed a commit to trailofbits/instafix-llvm that referenced this issue Mar 28, 2025
@gitoleg @xlauko
[CIR][CodeGen] handle zero init padding case (llvm#1257)
b799886 
I continue to use `csmith` and catch run time bags. Now it's time to fix
the layout for the const structs.

There is a divergence between const structs generated by CIR and the
original codegen. And this PR makes one more step to eliminate it. There
are cases where the extra padding is required - and here is a fix for
some of them. I did not write extra tests, since the fixes in the
existing already covers the code I added. The point is that now the
layout for all of these structs in the LLVM IR with and without CIR is
the same.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lattner lattner

Labels
bugzilla Issues migrated from bugzilla regression
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lattner @llvmbot