Skip to content

My contributions are still unacknowledged #385

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
Closed
llvmbot opened this issue Oct 8, 2003 · 5 comments
Closed

My contributions are still unacknowledged #385

llvmbot opened this issue Oct 8, 2003 · 5 comments
Labels
invalid Resolved as invalid, i.e. not a bug

Comments

@llvmbot
Copy link
Member

llvmbot commented Oct 8, 2003

Bugzilla Link 13
Resolution INVALID
Resolved on Nov 07, 2018 00:21
Version unspecified
OS Linux
Reporter LLVM Bugzilla Contributor
CC @FlashSheridan

Extended Description

I authored more than 90% of the code in LLVM, but that
guy Chris Lattner gets his name on all the papers.
And furthermore, I am not getting enough sunlight,
which impedes my mental faculties.
@llvmbot
Copy link
Member Author

llvmbot commented Oct 8, 2003

I suggest whispering subliminal hypnotic suggestions at Chris from your vantage
point on top of the filing cabinet. For now, though, there is nothing I can
directly do about this.

@llvmbot
Copy link
Member Author

llvmbot commented Jul 23, 2004

Oscar is now listed in the CREDITS.txt file:

http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040719/016365.html

This doesn't fix the paper publications; however, I'm sure there's much more
work that Oscar can do.

@froydnj
Copy link
Contributor

froydnj commented Nov 26, 2021

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

@Sairony
Copy link
Mannequin

Sairony mannequin commented Nov 27, 2021

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

@llvmbot
Copy link
Member Author

llvmbot commented Nov 27, 2021

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

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 1, 2021
@Quuxplusone Quuxplusone added the invalid Resolved as invalid, i.e. not a bug label Jan 20, 2022
pysuxing pushed a commit to pysuxing/llvm-project that referenced this issue Jul 17, 2024
@Lancern @lanza
[CIR] introduce CIR floating-point types (llvm#385)
b82fdb0 
This PR adds a dedicated `cir.float` type for representing
floating-point types. There are several issues linked to this PR: llvm#5,
llvm#78, and llvm#90.
pysuxing pushed a commit to pysuxing/llvm-project that referenced this issue Jul 17, 2024
@Lancern @lanza
[CIR] introduce CIR floating-point types (llvm#385)
ce57e0c 
This PR adds a dedicated `cir.float` type for representing
floating-point types. There are several issues linked to this PR: llvm#5,
llvm#78, and llvm#90.
keryell pushed a commit to keryell/llvm-project that referenced this issue Oct 19, 2024
@Lancern @lanza
[CIR] introduce CIR floating-point types (llvm#385)
169dab0 
This PR adds a dedicated `cir.float` type for representing
floating-point types. There are several issues linked to this PR: llvm#5,
xlauko pushed a commit to trailofbits/instafix-llvm that referenced this issue Mar 28, 2025
@Lancern @xlauko
[CIR] introduce CIR floating-point types (llvm#385)
1a784ca 
This PR adds a dedicated `cir.float` type for representing
floating-point types. There are several issues linked to this PR: #5,
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
invalid Resolved as invalid, i.e. not a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@froydnj @Quuxplusone @llvmbot