paolo@gcc.gnu.org wrote: > Is this still an issue with recent gcc releases (3.x, x>= 0)? I have not tested it myself, but Daniel Jacobowitz claims gcc version 3.2 still has this problem and I have no reason to believe differently. Here is a link to the post: http://groups.google.com/groups?selm=20021105142740.GA20877%40nevyn.them.org