https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
Richard Biener changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
--- Comment #6 from Richard Biener ---
(In reply to Andreas Schwab from comment #5)
> Why doesn't gcc warn about that?
It does:
unsigned char **q;
void foo (char *p)
{
q = (unsigned char **)&p;
}
> gcc t.c -fstrict-aliasing -Wstrict-aliasing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
--- Comment #5 from Andreas Schwab ---
Why doesn't gcc warn about that?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
--- Comment #4 from rguenther at suse dot de ---
On Thu, 1 Oct 2020, slyfox at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
>
> --- Comment #3 from Sergei Trofimovich ---
> Oh, that makes sense.
>
> > void __vfs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
--- Comment #3 from Sergei Trofimovich ---
Oh, that makes sense.
> void __vfscanf_internal__ (const char *f, __builtin_va_list argptr)
> {
> /* assume input: "1<>\0" */
> while (*f != '\0')
> {
> const unsigned char ** pstr = (cons
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
Richard Biener changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264
--- Comment #1 from Sergei Trofimovich ---
Created attachment 49295
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49295&action=edit
uname.c
