https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
--- Comment #8 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #7)
> (In reply to cqwrteur from comment #6)
> > (In reply to Andrew Pinski from comment #5)
> > > Dup of bug 101785 really. There is no supported at all included.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
--- Comment #7 from Andrew Pinski ---
(In reply to cqwrteur from comment #6)
> (In reply to Andrew Pinski from comment #5)
> > Dup of bug 101785 really. There is no supported at all included.
> >
> > *** This bug has been marked as a duplicate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
--- Comment #6 from cqwrteur ---
(In reply to Andrew Pinski from comment #5)
> Dup of bug 101785 really. There is no supported at all included.
>
> *** This bug has been marked as a duplicate of bug 101785 ***
but i am sure __NR_newfstatat do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
--- Comment #4 from cqwrteur ---
(In reply to Andrew Pinski from comment #3)
> This is a bug in android headers.
>
> I really doubt anyone really cares enough about gcc support for android
> these days. I also really double anyone has really p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
--- Comment #3 from Andrew Pinski ---
This is a bug in android headers.
I really doubt anyone really cares enough about gcc support for android these
days. I also really double anyone has really ported aarch64 android support to
gcc. Google mo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
--- Comment #2 from cqwrteur ---
Created attachment 51264
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51264&action=edit
more errors
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101784
--- Comment #1 from cqwrteur ---
Created attachment 51263
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51263&action=edit
log file
