Hi Timo. First of all, thanks for the bug report. > (If I report this bug against "gnat-4.3" I won't get email if "gnat-4.4" > enters debian and > fixes this bug.)
You can subscribe to the bug; see http://www.debian.org/Bugs/Developer#subscribe for instructions. The life cycle is usually: - new bug opened against gnat-4.4 - bug forwarded upstream - bug closed upstream - bug tagged fixed-upstream and retitled [Fixed in 4.4] - fix backported into gnat-4.3 and bug closed, or: - bug reassigned to gnat-4.4 and closed with a new upload of gnat-4.4 By subscribing to the bug you will be notified of all these changes automatically. At this point I would like to know whether this bug exists in upstream GCC. There has been a similar but not identical bug in the past (see http://gcc.gnu.org/PR32452). -- Ludovic Brenta. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
