From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A compiler bug
Date: Wed, 1 Aug 2018 17:27:30 -0700 [thread overview]
Message-ID: <079A451E-7BFC-4E52-99AA-2E58449C1346@bitblocks.com> (raw)
In-Reply-To: <CAOw7k5jsW0WUTaqE1N_L5_2KVyvxLt74=Nwrd5JTOuRnNGQSuw@mail.gmail.com>
On Aug 1, 2018, at 4:35 PM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
> even so, the format and intention of the example seems practical (with the correct cast to uintptr) and "An implementation may accept other forms of constant expressions".
> it should be fairly easy to add as an extension with consistent handling across ?c.
Both gcc and clang handle this case. This example was derived from
ObjectIcon (it works on plan9/x86 & unix systems but not on plan9/arm).
I am not familiar with the C compiler sources but will take a look.
Thanks for your response.
next prev parent reply other threads:[~2018-08-02 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 7:21 Bakul Shah
2018-08-01 23:35 ` Charles Forsyth
2018-08-02 0:27 ` Bakul Shah [this message]
2018-08-02 9:38 ` Charles Forsyth
2018-08-02 13:28 ` Benjamin Purcell
2018-08-02 14:20 cinap_lenrek
2018-08-05 14:53 ` Charles Forsyth
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=079A451E-7BFC-4E52-99AA-2E58449C1346@bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).