public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alex.wolf at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/50909] Process "#pragma options align=reset" correctly on Mac OS X
Date: Mon, 23 Jun 2014 15:48:00 -0000	[thread overview]
Message-ID: <bug-50909-4-NX6eDiQWdT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50909-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50909

--- Comment #8 from Alex <alex.wolf at gmail dot com> ---
I am writing cross platform code with some platform specific USB enumeration
functionality. IOKit was just what I needed on the mac, libudev on linux. I
inevitably stumbled over this issue when trying to compile the mac portion. 

I think it would be sad if gcc wouldn't support these deviations from the
standard in the future, considering anybody trying to use IOKit with gcc will
come across this "bug".

Are you saying I should not use gcc on a mac with IOKit?
If I should, then gcc should not give me such an error. It is easy to work
around but why punish the developer when Apple wrote the non-compliant header
that IOKit users must include.
I think this is a clear case where gcc could & should change its leniency for
the sake of its developers. Or, am I supposed to write my own USB library from
the ground up for mac just because the pragmas aren't supported? 


I "fixed" my setup without recompiling gcc:
I made a backup of USB.h and then changed all occurrences of

#pragma options align=reset

to 

#pragma pack()

which seemed to compile and run. 

As to someone implementing clang behavior: I was under the impression that the
attached patch just needed to be applied? That is why I was inquiring as to why
nobody had applied it after 3 years.


  parent reply	other threads:[~2014-06-23 15:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29  5:03 [Bug objc/50909] New: " carsomyr at gmail dot com
2012-05-23 21:35 ` [Bug objc/50909] " carl at lytro dot com
2012-08-08  8:26 ` roman at qubyx dot com
2013-09-13 18:53 ` dc7000 at att dot com
2013-09-13 19:05 ` dominiq at lps dot ens.fr
2013-09-13 20:32 ` dc7000 at att dot com
2014-06-23 14:52 ` dominiq at lps dot ens.fr
2014-06-23 15:48 ` alex.wolf at gmail dot com [this message]
2014-06-23 16:30 ` manu at gcc dot gnu.org
2021-10-25 11:01 ` emmiller at gmail dot com
2024-06-16 18:44 ` vital.had at gmail dot com

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-50909-4-NX6eDiQWdT@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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: link
Be 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).