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

Support bitwidth attribute in llvm-gcc #1656

Closed
llvmbot opened this issue Mar 28, 2007 · 5 comments
Closed

Support bitwidth attribute in llvm-gcc #1656

llvmbot opened this issue Mar 28, 2007 · 5 comments
Labels
bugzilla Issues migrated from bugzilla enhancement Improving things as opposed to bug fixing, e.g. new or missing feature llvm-tools All llvm tools that do not have corresponding tag wontfix Issue is real, but we can't or won't fix it. Not invalid

Comments

@llvmbot
Copy link
Member

llvmbot commented Mar 28, 2007

Bugzilla Link 1284
Resolution WONTFIX
Resolved on Jul 29, 2010 17:26
Version trunk
OS All
Reporter LLVM Bugzilla Contributor
CC @lattner

Extended Description

The llvm-gcc tool should support a bitwidth attribute that permits arbitrary
precision bit width integers to be used. This PR is to track the development of
that feature.

As with other type attributes, this feature requests that:

attribute((bitwidth(N)))

be recognized by llvm-gcc so that things like:

typedef int attribute((bitwidth(23))

could be used to make a signed 23 bit integer.
@llvmbot
Copy link
Member Author

llvmbot commented Apr 26, 2007

This won't happen for 2.0

@llvmbot
Copy link
Member Author

llvmbot commented May 18, 2007

The code for this feature and related ones is done. It includes the beginnings
of APIntification of llvm-gcc (to represent integer constants with APInt instead
of with a pair of HOST_WIDE_INT) as well as several builtin functions for
manipulating integers of various bit widths.

The patch for this will be submitted sometime in the 2.1 time frame.

@llvmbot
Copy link
Member Author

llvmbot commented Jan 15, 2008

Hi Chris and Reid,

Is it the time to commit the patch after public review ?

Sheng.

@lattner
Copy link
Collaborator

lattner commented Jan 15, 2008

Please wait until after 2.2 branches (wednesday), we are working on stabilizing things right now.

@lattner
Copy link
Collaborator

lattner commented Jul 30, 2010

We don't plan to do this in llvm-gcc.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
@Quuxplusone Quuxplusone added the wontfix Issue is real, but we can't or won't fix it. Not invalid label Jan 20, 2022
@Endilll Endilll added enhancement Improving things as opposed to bug fixing, e.g. new or missing feature and removed new-feature labels Aug 15, 2023
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 enhancement Improving things as opposed to bug fixing, e.g. new or missing feature llvm-tools All llvm tools that do not have corresponding tag wontfix Issue is real, but we can't or won't fix it. Not invalid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Quuxplusone @Endilll @lattner @llvmbot