From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: David Brown <david.brown@hesbynett.no>
Cc: Martin Uecker <uecker@tugraz.at>,
gcc@gcc.gnu.org, Richard Biener <richard.guenther@gmail.com>
Subject: Re: aliasing
Date: Mon, 18 Mar 2024 10:09:49 +0000 [thread overview]
Message-ID: <CAH6eHdSHc10R8f7g2rQasD=yHKe8q6-jEW6L=GrixUj=uAyn2A@mail.gmail.com> (raw)
In-Reply-To: <c29bbf97-6dd3-717f-17ee-e2bf6ffdb18b@hesbynett.no>
On Mon, 18 Mar 2024 at 09:01, David Brown wrote:
> Should it also include "uint8_t" (if it exists) ? "uint8_t" is often an
> alias for "unsigned char", but it could be something different, like an
> alias for __UINT8_TYPE__, or "unsigned int
> __attribute__((mode(QImode)))", which is used in the AVR gcc port.
N.B. __UINT8_TYPE__ is not a type, it's just a macro that expands to
something else (like unsigned char).
next prev parent reply other threads:[~2024-03-18 10:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 7:03 aliasing Martin Uecker
2024-03-18 8:26 ` aliasing Richard Biener
2024-03-18 10:55 ` aliasing Martin Uecker
2024-03-18 11:56 ` aliasing Martin Uecker
2024-03-18 13:21 ` aliasing Richard Biener
2024-03-18 15:13 ` aliasing Martin Uecker
2024-03-18 9:00 ` aliasing David Brown
2024-03-18 10:09 ` Jonathan Wakely [this message]
2024-03-18 11:41 ` aliasing Martin Uecker
2024-03-18 13:29 ` aliasing David Brown
2024-03-18 13:54 ` aliasing Andreas Schwab
2024-03-18 16:46 ` aliasing David Brown
2024-03-18 16:55 ` aliasing David Brown
2024-03-18 15:00 ` aliasing Martin Uecker
2024-03-18 17:11 ` aliasing David Brown
-- strict thread matches above, loose matches on Subject: below --
1999-08-21 9:23 aliasing Jason Moxham
1999-08-21 9:46 ` aliasing Mark Mitchell
1999-08-31 23:20 ` aliasing Mark Mitchell
1999-08-31 23:20 ` aliasing Jason Moxham
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='CAH6eHdSHc10R8f7g2rQasD=yHKe8q6-jEW6L=GrixUj=uAyn2A@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=david.brown@hesbynett.no \
--cc=gcc@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=uecker@tugraz.at \
/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).