This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ada/52110] s-osinte.ads:447:09: "clockid_t" conflicts with declaration at line 194
- From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 05 Feb 2012 19:12:36 +0000
- Subject: [Bug ada/52110] s-osinte.ads:447:09: "clockid_t" conflicts with declaration at line 194
- Auto-submitted: auto-generated
- References: <bug-52110-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52110
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-02-05
CC| |ebotcazou at gcc dot
| |gnu.org
Ever Confirmed|0 |1
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-02-05 19:12:36 UTC ---
> Attached is a possible patch. On "most" PARISC machines, reads and
> writes are strongly ordered and possibly this meets the "atomic" requirement.
Not entirely I think, since the object is 64-bit wide. Of course, it's a
little annoying to discover years later that the implementation wasn't really
correct.
So I'd leave s-taspri-hpux-dce.ads unchanged and just comment out the second
pragma Atomic, with a ??? saying that, historically, the pragma had been
silently accepted but actually ineffective.