Bugzilla CPU targets

Bugzilla CPU targets

[H. J. Lu]

One thing I missed the most is CPU targets. Can we add ia32, ia64,
mips, alpha, ppc, .....?


H.J.

Re: Bugzilla CPU targets

[Andreas Jaeger]

"H. J. Lu" <hjl@lucon.org> writes:

> One thing I missed the most is CPU targets. Can we add ia32, ia64,
> mips, alpha, ppc, .....?

You can search for host/target/build, isn't that enough?

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Re: Bugzilla CPU targets

[H. J. Lu]

On Thu, May 22, 2003 at 08:54:31AM +0200, Andreas Jaeger wrote:
> "H. J. Lu" <hjl@lucon.org> writes:
> 
> > One thing I missed the most is CPU targets. Can we add ia32, ia64,
> > mips, alpha, ppc, .....?
> 
> You can search for host/target/build, isn't that enough?
> 

You can make your own host/target/build. What I like to see a drop
down menu to select the valid ones. Also in most cases, a backend bug
is indepedent of host/target/build OSes.


H.J.

Re: Bugzilla CPU targets

[H. J. Lu]

On Thu, May 22, 2003 at 12:02:16AM -0700, H. J. Lu wrote:
> On Thu, May 22, 2003 at 08:54:31AM +0200, Andreas Jaeger wrote:
> > "H. J. Lu" <hjl@lucon.org> writes:
> > 
> > > One thing I missed the most is CPU targets. Can we add ia32, ia64,
> > > mips, alpha, ppc, .....?
> > 
> > You can search for host/target/build, isn't that enough?
> > 
> 
> You can make your own host/target/build. What I like to see a drop
> down menu to select the valid ones. Also in most cases, a backend bug
> is indepedent of host/target/build OSes.
> 

BTW, there is a target field in query page, which looks like what I am
looking for. But it has 3.3.1, 3.4, instead of ia32, ia64, ... There
is no target in bug entry page.


H.J.

Re: Bugzilla CPU targets

[Daniel Berlin]

On Thursday, May 22, 2003, at 03:02  AM, H. J. Lu wrote:

> On Thu, May 22, 2003 at 08:54:31AM +0200, Andreas Jaeger wrote:
>> "H. J. Lu" <hjl@lucon.org> writes:
>>
>>> One thing I missed the most is CPU targets. Can we add ia32, ia64,
>>> mips, alpha, ppc, .....?
>>
>> You can search for host/target/build, isn't that enough?
>>
>
> You can make your own host/target/build. What I like to see a drop
> down menu to select the valid ones.


This is probably impractical.
Too many combinations.
Even if you *could* do it, it would probably be about 100k of html to 
just list the values.
You can't just do it in javascript, as not everyone has javascript.

>  Also in most cases, a backend bug
> is indepedent of host/target/build OSes.
>
>
> H.J.

Re: Bugzilla CPU targets

[Andrew Pinski]

What about just listing CPU, OS separately, and not worry about invalid 
combinations as we can change then easy, I think keywords will work for 
this?

Thanks,
Andrew Pinski

On Thursday, May 22, 2003, at 10:38 US/Eastern, Daniel Berlin wrote:

>
> On Thursday, May 22, 2003, at 03:02  AM, H. J. Lu wrote:
>
>> On Thu, May 22, 2003 at 08:54:31AM +0200, Andreas Jaeger wrote:
>>> "H. J. Lu" <hjl@lucon.org> writes:
>>>
>>>> One thing I missed the most is CPU targets. Can we add ia32, ia64,
>>>> mips, alpha, ppc, .....?
>>>
>>> You can search for host/target/build, isn't that enough?
>>>
>>
>> You can make your own host/target/build. What I like to see a drop
>> down menu to select the valid ones.
>
>
> This is probably impractical.
> Too many combinations.
> Even if you *could* do it, it would probably be about 100k of html to 
> just list the values.
> You can't just do it in javascript, as not everyone has javascript.
>
>>  Also in most cases, a backend bug
>> is indepedent of host/target/build OSes.
>>
>>
>> H.J.
>
>
>

Re: Bugzilla CPU targets

[H. J. Lu]

On Thu, May 22, 2003 at 10:38:54AM -0400, Daniel Berlin wrote:
> 
> On Thursday, May 22, 2003, at 03:02  AM, H. J. Lu wrote:
> 
> > On Thu, May 22, 2003 at 08:54:31AM +0200, Andreas Jaeger wrote:
> >> "H. J. Lu" <hjl@lucon.org> writes:
> >>
> >>> One thing I missed the most is CPU targets. Can we add ia32, ia64,
> >>> mips, alpha, ppc, .....?
> >>
> >> You can search for host/target/build, isn't that enough?
> >>
> >
> > You can make your own host/target/build. What I like to see a drop
> > down menu to select the valid ones.
> 
> 
> This is probably impractical.
> Too many combinations.
> Even if you *could* do it, it would probably be about 100k of html to 
> just list the values.
> You can't just do it in javascript, as not everyone has javascript.

I am talking about targets in gcc/gcc/config. I counted there are
34 different cpus. You don't worry about OSes. There are still
host/target/build fields.


H.J.

Re: Bugzilla CPU targets

[Joseph S. Myers]

On Thu, 22 May 2003, H. J. Lu wrote:

> I am talking about targets in gcc/gcc/config. I counted there are
> 34 different cpus. You don't worry about OSes. There are still
> host/target/build fields.

We could revisit splitting the "target" component into separate components
for different targets (at least those targets with active maintainers and
users) - so that, for target-specific bugs in "target", we don't need to
overload the bug subject line with a target name.

-- 
Joseph S. Myers
jsm28@cam.ac.uk