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

Chris Is Buggy #1372

Closed
llvmbot opened this issue Nov 11, 2006 · 21 comments
Closed

Chris Is Buggy #1372

llvmbot opened this issue Nov 11, 2006 · 21 comments
Assignees
Labels
bugzilla Issues migrated from bugzilla llvm-tools All llvm tools that do not have corresponding tag regression wontfix Resolved as "WON'T FIX." Not "INVALID" — the issue is real, but we can't or won't fix it

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Nov 11, 2006

Bugzilla Link 1000
Resolution WONTFIX
Resolved on May 24, 2011 11:55
Version trunk
OS All
Depends On llvm/llvm-bugzilla-archive#10000
Reporter LLVM Bugzilla Contributor
CC @lattner,@isanbard

Extended Description

There's no known fix for this bug.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 11, 2006

assigned to @tlattner

@lattner
Copy link
Collaborator

lattner commented Nov 11, 2006

I could have sworn he worked at one point.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 11, 2006

Our internal bug tracking software requires submitter to classify bug. Available options are : Security,
Performance, Serious Bug, Data loss, new feature.

Pick one!

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 11, 2006

Is there an option for "All of the above" ?

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 11, 2006

If there's no such option, Serious Bug seems to be the most fitting for the
levity of this PR.

@lattner
Copy link
Collaborator

lattner commented Nov 11, 2006

If bug 100 couldn't be fixed, what do you think the chances of fixing this one are?

-Chris

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 11, 2006

I don't know, but not fixing it is not an option!

@isanbard
Copy link
Contributor

isanbard commented Nov 11, 2006

We really should categorize these correctly. Marking this as a tool. Also, because Chris is a Common Code
Generator, it's believed that the problem's in his internal code.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 11, 2006

This definitely happens on ALL Platforms and All Operating Systems.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 12, 2006

I know some people (actually 3) who might be able to fix him. He can be turned
into the proper open source compiler guru:
http://www.webweavertech.com/ovidiu/weblog/gallery/richard-stallman/richard-stallman-Images/1.jpg

But this is Tonya's call since she has to live with him. I suspect this will be
a p4later, err, I mean WONTFIX.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 12, 2006

Based on the foregoing, fixing this is looking to be hard. I suggest we start
with containment. While we may not be able to get to the root cause of the
problem quickly, perhaps we can diminish or eliminate the viral effects it has
on the project. So, here's some suggestions to get started:

  1. Everyone stop talking to Chris immediately.
  2. With Tanya's help, perhaps we can unplug Chris during off hours.
  3. Everything Chris does needs to be code reviewed by everybody (except Chris).
  4. Definitely no more Lattners on the project.

Any other impact reducing ideas?

:)

@nlewycky
Copy link
Contributor

nlewycky commented Nov 12, 2006

Ah, there's nothing buggy with Chris that a couple of beers couldn't fix!

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 12, 2006

So, you think the fix to this is free? As in free beer?

@lattner
Copy link
Collaborator

lattner commented Nov 12, 2006

  1. We could revert all of Chris' code?

@lattner
Copy link
Collaborator

lattner commented Nov 18, 2006

I don't think this is fixable.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 18, 2006

It may not be fixable, but WORKSFORME? I don't think so, mister.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Nov 18, 2006

This is much more appropriate.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Aug 13, 2010

Dale asked me to test Bugzilla, and picked this one (?). Ergo, this is a test comment.

@tlattner
Copy link
Contributor

tlattner commented Aug 13, 2010

Why are you testing bugzilla?

@llvmbot
Copy link
Collaborator Author

llvmbot commented Aug 13, 2010

Dale said that Bugzilla wasn't working for him, and he asked me to add a comment to some bug, and when I insisted on a number, he chose this one.

@tlattner
Copy link
Contributor

tlattner commented Aug 13, 2010

Ok, well, let me know if its still a problem. I've had one other person say they couldnt respond to certain bugs, so just wanted to know if it was a trend or not.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
@Quuxplusone Quuxplusone added the wontfix Resolved as "WON'T FIX." Not "INVALID" — the issue is real, but we can't or won't fix it label Jan 20, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugzilla Issues migrated from bugzilla llvm-tools All llvm tools that do not have corresponding tag regression wontfix Resolved as "WON'T FIX." Not "INVALID" — the issue is real, but we can't or won't fix it
Projects
None yet
Development

No branches or pull requests

6 participants