Dear GCC maintainers (and Martin in particular), I have reason to believe that lam, which was uploaded to unstable to use gfortran after this bug was found, is also affected by this bug, from [1]. Could you confirm that this is the case? Thank you. Kumar [1]: http://buildd.debian.org/fetch.cgi?pkg=lam&arch=alpha&ver=7.1.2-1.2&stamp=1202605929&file=log&as=raw -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036
Attachment:
signature.asc
Description: Digital signature