Bugzilla Component for CUDA Bugs in Clang

Clang Frontend
1

Could someone create a component for CUDA bugs in Clang? I wanted to report a CUDA-related bug but didn’t manage to find a suitable component in https://llvm.org/bugs/describecomponents.cgi?product=clang

Thanks,
Jingyue

2

I was about to +1 this, but then I looked through the existing list of
components, and it doesn't seem that there are components for other
similarly-sized projects, like OpenMP or whatever. So maybe we can
just get by with putting "CUDA" in the summary? Bugzilla search
sucks, but even it can handle this. :slight_smile:

What do you think?

3

I was about to +1 this, but then I looked through the existing list of
components, and it doesn't seem that there are components for other
similarly-sized projects, like OpenMP or whatever. So maybe we can
just get by with putting "CUDA" in the summary? Bugzilla search
sucks, but even it can handle this. :slight_smile:

Actually, OpenMP is a separate "product" in the Bugzilla, even more
high-level than "component".

What do you think?

I am fine with squeezing CUDA bugs in C++. I was just confused when I
searched through the list and didn't find a place for CUDA bugs. Maybe
rename "C++" to "C++/CUDA"?

4

I was about to +1 this, but then I looked through the existing list of
components, and it doesn't seem that there are components for other
similarly-sized projects, like OpenMP or whatever. So maybe we can
just get by with putting "CUDA" in the summary? Bugzilla search
sucks, but even it can handle this. :slight_smile:

Actually, OpenMP is a separate "product" in the Bugzilla, even more
high-level than "component".

Right, but it also covers the runtime implementation.

What do you think?

I am fine with squeezing CUDA bugs in C++. I was just confused when I
searched through the list and didn't find a place for CUDA bugs. Maybe
rename "C++" to "C++/CUDA"?

I'd vote for a new CUDA component.

5

I'd vote for a new CUDA component.

I guess this would let us watch the CUDA component for new bugs, which
scales better than hoping that people cc the right people. I'm
onboard with that.

6

From: "Justin Lebar via cfe-dev" <cfe-dev@lists.llvm.org>
To: "Reid Kleckner" <rnk@google.com>
Cc: "cfe-dev" <cfe-dev@lists.llvm.org>
Sent: Friday, February 5, 2016 2:58:10 PM
Subject: Re: [cfe-dev] Bugzilla Component for CUDA Bugs in Clang

> I'd vote for a new CUDA component.

I guess this would let us watch the CUDA component for new bugs,
which
scales better than hoping that people cc the right people. I'm
onboard with that.

Yes, please add a new component. We've been bad about this, historically, but that's no excuse to not be better going forward.

-Hal

7

+Tanya, Anton, who may be able to effect this.

8

CUDA component under what Product?

I’ll also need below. However, I can use the defaults for the product you put it under for default assignee and cc list if you don’t have someone. Usually its a dummy assignee and the llvmbugs list.

-Tanya

9

Since we already have the necessary parties involved, a quick shout out for https://llvm.org/bugs/show_bug.cgi?id=26479 to add a Phabricator component.

10

CUDA component under what Product?

Clang

I’ll also need below.

Component description: CUDA front-end in clang

(Or, if you prefer, “Issues relating to the CUDA front-end in clang”.)

I can use the defaults for the product you put it under for default assignee and cc list if you don’t have someone. Usually its a dummy assignee and the llvmbugs list.

sgtm

Thank you very much.

11

Done.

-Tanya

12

I did not see a response to this. Please let me know if I missed it.

-Tanya

13

Er, I see both Justin’s response, and you saying “Done”?

14

Yeah, just got confused with an old email. Disregard :slight_smile:

-Tanya