public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31657] New: __attribute__((pure)) etc. in installed headers Date: Fri, 19 Apr 2024 16:33:37 +0000 [thread overview] Message-ID: <bug-31657-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31657 Bug ID: 31657 Summary: __attribute__((pure)) etc. in installed headers Product: glibc Version: 2.40 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: jakub at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- I see grep __attribute__ `rpm -ql glibc-headers-x86` 2>/dev/null | grep -v '((__' /usr/include/bits/types/res_state.h: __attribute__((packed)); /usr/include/sys/platform/x86.h: __attribute__ ((pure)); and can see it even on latest glibc trunk: find [^o]* -name res_state.h | xargs grep __attribute__ resolv/bits/types/res_state.h: __attribute__((packed)); find [^o]* -name \*.h | grep /platform/ | xargs grep __attribute__ sysdeps/x86/sys/platform/x86.h: __attribute__ ((pure)); Guess it should be __attribute_pure__ or __attribute__ ((__pure__)) and __attribute__((__packed__)) instead for namespace reasons. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-04-19 16:33 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-19 16:33 jakub at redhat dot com [this message] 2024-04-19 16:34 ` [Bug libc/31657] " jakub at redhat dot com 2024-04-19 17:15 ` schwab@linux-m68k.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31657-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).