Re: Rationale for an old TRUNCATE patch

2009-06-17 Thread Adam Nemet
Jeff Law writes: Ian Lance Taylor wrote: Adam Nemet ane...@caviumnetworks.com writes: I am trying to understand the checkin by Jeff Law from about 11 years ago: r19204 | law | 1998-04-14 01:04:21 -0700 (Tue, 14 Apr 1998) | 4 lines * combine.c

Re: Rationale for an old TRUNCATE patch

2009-06-17 Thread Adam Nemet
Ian Lance Taylor writes: truncate has a machine independent meaning. Yes, I guess with your definition below it does. It's interesting though that Jim had said the opposite in the excerpts posted by Jeff: And a later message from Jim: Truncate converts a value from a larger to a smaller

Re: Rationale for an old TRUNCATE patch

2009-06-17 Thread Ian Lance Taylor
Adam Nemet ane...@caviumnetworks.com writes: Ian Lance Taylor writes: truncate has a machine independent meaning. Yes, I guess with your definition below it does. It's interesting though that Jim had said the opposite in the excerpts posted by Jeff: And a later message from Jim:

Re: Rationale for an old TRUNCATE patch

2009-06-17 Thread Jeff Law
Adam Nemet wrote: Jeff Law writes: Ian Lance Taylor wrote: Adam Nemet ane...@caviumnetworks.com writes: I am trying to understand the checkin by Jeff Law from about 11 years ago: r19204 | law | 1998-04-14 01:04:21 -0700 (Tue, 14 Apr 1998) | 4 lines *

Re: Rationale for an old TRUNCATE patch

2009-06-17 Thread Adam Nemet
Ian Lance Taylor writes: I'm not entirely sure, but I don't think Jim said the opposite. He said that the way truncate works is machine dependent. I said that the output of truncate is machine independent. Since truncate is only defined for fixed-point modes, I think both statements are

Re: Rationale for an old TRUNCATE patch

2009-06-17 Thread Ian Lance Taylor
Adam Nemet ane...@caviumnetworks.com writes: Ian Lance Taylor writes: I'm not entirely sure, but I don't think Jim said the opposite. He said that the way truncate works is machine dependent. I said that the output of truncate is machine independent. Since truncate is only defined for

Rationale for an old TRUNCATE patch

2009-06-16 Thread Adam Nemet
I am trying to understand the checkin by Jeff Law from about 11 years ago: r19204 | law | 1998-04-14 01:04:21 -0700 (Tue, 14 Apr 1998) | 4 lines * combine.c (simplify_rtx, case TRUNCATE): Respect value of TRULY_NOOP_TRUNCATION. Index: combine.c

Re: Rationale for an old TRUNCATE patch

2009-06-16 Thread Ian Lance Taylor
Adam Nemet ane...@caviumnetworks.com writes: I am trying to understand the checkin by Jeff Law from about 11 years ago: r19204 | law | 1998-04-14 01:04:21 -0700 (Tue, 14 Apr 1998) | 4 lines * combine.c (simplify_rtx, case TRUNCATE): Respect value of

Re: Rationale for an old TRUNCATE patch

2009-06-16 Thread Adam Nemet
Ian Lance Taylor writes: I agree that this patch looks wrong in todays compiler. There should be no need to call TRULY_NOOP_TRUNCATION if you are in a TRUNCATE anyhow. Thanks. Do you think we can assume this for TRUNCATEs in general or only for MIPS-like TRUNCATEs? I can't think of why it

Re: Rationale for an old TRUNCATE patch

2009-06-16 Thread Ian Lance Taylor
Adam Nemet ane...@caviumnetworks.com writes: Ian Lance Taylor writes: I agree that this patch looks wrong in todays compiler. There should be no need to call TRULY_NOOP_TRUNCATION if you are in a TRUNCATE anyhow. Thanks. Do you think we can assume this for TRUNCATEs in general or only for

Re: Rationale for an old TRUNCATE patch

2009-06-16 Thread Jeff Law
Adam Nemet wrote: I am trying to understand the checkin by Jeff Law from about 11 years ago: r19204 | law | 1998-04-14 01:04:21 -0700 (Tue, 14 Apr 1998) | 4 lines * combine.c (simplify_rtx, case TRUNCATE): Respect value of TRULY_NOOP_TRUNCATION.

Re: Rationale for an old TRUNCATE patch

2009-06-16 Thread Jeff Law
Ian Lance Taylor wrote: Adam Nemet ane...@caviumnetworks.com writes: I am trying to understand the checkin by Jeff Law from about 11 years ago: r19204 | law | 1998-04-14 01:04:21 -0700 (Tue, 14 Apr 1998) | 4 lines * combine.c (simplify_rtx, case TRUNCATE): Respect