[Bug libstdc++/31554] stable_partition assumes iterator difference type is always ptrdiff_t

--- Comment #3 from djg at cray dot com 2007-04-12 21:53 --- (In reply to comment #2) At a glance, that looks right to me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31554

[Bug libstdc++/31556] New: find_if uses operator! instead of conversion to bool

+ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: djg at cray dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31556

[Bug libstdc++/31555] stable_partition assumes iterator difference type is always ptrdiff_t

--- Comment #1 from djg at cray dot com 2007-04-12 19:09 --- *** This bug has been marked as a duplicate of 31554 *** -- djg at cray dot com changed: What|Removed |Added

[Bug libstdc++/31554] stable_partition assumes iterator difference type is always ptrdiff_t

--- Comment #1 from djg at cray dot com 2007-04-12 19:09 --- *** Bug 31555 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31554

[Bug libstdc++/31555] New: stable_partition assumes iterator difference type is always ptrdiff_t

Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: djg at cray dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31555

[Bug libstdc++/31554] New: stable_partition assumes iterator difference type is always ptrdiff_t

Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: djg at cray dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31554

[Bug tree-optimization/29145] unsafe use of restrict qualifier

--- Comment #10 from djg at cray dot com 2007-01-26 21:09 --- (In reply to comment #8) > I'm testing this patch, that makes us more conservative, and concludes that > two > pointers don't overlap only if both are "based on" restricted pointers, with >

[Bug tree-optimization/29145] unsafe use of restrict qualifier

--- Comment #7 from djg at cray dot com 2006-11-05 16:50 --- (In reply to comment #5) "based on" basically means copied from, and possibly incremented or decremented, though not necessarily in obvious ways. Your example is legal; q is based on p. BTW, I made a mistake in

[Bug tree-optimization/29145] unsafe use of restrict qualifier

--- Comment #2 from djg at cray dot com 2006-09-20 23:49 --- The definition of restrict in C99 6.7.3.1 doesn't say that only the original restrict-qualified pointer can be used to access the object it points to; it says that any pointer "based on" the original restrict-qu

[Bug tree-optimization/29145] New: unsafe use of restrict qualifier

e use of restrict qualifier Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: djg at cray dot com GCC build

[Bug libstdc++/28414] New: return type of valarray's sqrt function isn't valarray

ority: P3 Component: libstdc++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: djg at cray dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28414