This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Bug summary notations (Was Re: [Bug target/11260] [alpha] 'output_operand: floating constant misused' with sqrt(0.0) and -mcpu=ev6)


I'm confused about the need to put [alpha] in front of the summary here.
Remind me again why it makes sense?
You can search for  host/target/build containing alpha quite easily.
At least one of these will show up on the summary.
If even *this* isn't enough, you can use a keyword.

So why is it in the summary?
It's not like regression tracking, which arguably has a need for it.

On Thursday, June 19, 2003, at 08:48 PM, falk at debian dot org wrote:

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11260


falk at debian dot org changed:


What |Removed |Added
----------------------------------------------------------------------- -----
Summary|code causes 'output_operand:|[alpha] 'output_operand:
|floating constant misused' |floating constant misused'
|under |with sqrt(0 dot 0) and -
| |mcpu=ev6



------- Additional Comments From falk at debian dot org 2003-06-20 00:48 -------
Here's a C test case:


double f(void)
{
    return sqrt(0.0);
}

The ICE does not happen with mainline, most likely because of Roger's sqrt
constant folding stuff.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]