We noticed that in the headers cstdio and cstdlib the c99 keyword "restrict" is
used unconditionally. AFAICS it should be used here __restrict instead.
By user-report - I've got - it leads to the issue that the "restrict" keyword
gets interpreted as argument name for non c99.


-- 
           Summary: in cstdio/cstdlib keyword restrict is used instead of
                    __restrict
           Product: gcc
           Version: 4.5.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ktietz at gcc dot gnu dot org
GCC target triplet: x86_64-*-* i686-*-*


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45300

Reply via email to