public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnugcc at marino dot st" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/60411] ADA bootstrap failure on ARM
Date: Tue, 08 Apr 2014 21:27:00 -0000 [thread overview]
Message-ID: <bug-60411-4-NqXx5Kfme3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60411-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60411
John Marino <gnugcc at marino dot st> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gnugcc at marino dot st
--- Comment #11 from John Marino <gnugcc at marino dot st> ---
Eric,
Thanks for these commits. However, I'm still unable to build
arm-aux-linux-androideabi cross-compiler target after 209227.
This is the current error:
s-osinte.ads:593:07: component "sa_flags" overlaps "sa_mask" at line 592
This happens when a-dynpri.adb is being compiled. s-osinte.ads is
s-osinte-android.ads of course.
I think this is a direct consequence of #include <asm/signal.h> at sigtramp.h
s-ointe-android.ads, lines 590-594:
for struct_sigaction use record
sa_handler at Linux.sa_handler_pos range 0 .. Standard'Address_Size - 1;
sa_mask at Linux.sa_mask_pos range 0 .. 1023;
sa_flags at Linux.sa_flags_pos range 0 .. Standard'Address_Size - 1;
end record;
asm/signal.h (NDK, API 15):
typedef unsigned long sigset_t;
struct sigaction {
union {
__sighandler_t _sa_handler;
void (*_sa_sigaction)(int, struct siginfo *, void *);
} _u;
sigset_t sa_mask;
unsigned long sa_flags;
void (*sa_restorer)(void);
};
So it does seem that struct_sigaction record isn't correct after all.
John
next prev parent reply other threads:[~2014-04-08 21:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 13:54 [Bug ada/60411] New: ADA canadian cross build fails bernd.edlinger at hotmail dot de
2014-03-04 17:24 ` [Bug ada/60411] " mikpelinux at gmail dot com
2014-03-06 14:22 ` bernd.edlinger at hotmail dot de
2014-03-07 20:36 ` [Bug ada/60411] ADA bootstrap failure on ARM charlet at gcc dot gnu.org
2014-03-07 20:57 ` bernd.edlinger at hotmail dot de
2014-03-10 12:48 ` bernd.edlinger at hotmail dot de
2014-03-10 13:26 ` Arnaud Charlet
2014-03-10 13:27 ` charlet at adacore dot com
2014-04-08 8:24 ` ebotcazou at gcc dot gnu.org
2014-04-08 9:04 ` ebotcazou at gcc dot gnu.org
2014-04-08 20:35 ` ebotcazou at gcc dot gnu.org
2014-04-08 21:27 ` gnugcc at marino dot st [this message]
2014-04-08 21:49 ` gnugcc at marino dot st
2014-04-09 7:58 ` ebotcazou at gcc dot gnu.org
2014-04-09 7:59 ` ebotcazou at gcc dot gnu.org
2014-04-09 8:02 ` [Bug ada/60411] Ada " ebotcazou at gcc dot gnu.org
2014-04-09 9:58 ` gnugcc at marino dot st
2014-04-09 12:46 ` gnugcc at marino dot st
2014-04-09 13:02 ` ebotcazou at gcc dot gnu.org
2014-04-09 13:27 ` gnugcc at marino dot st
2014-04-09 13:48 ` ebotcazou at gcc dot gnu.org
2014-04-10 9:52 ` gnugcc at marino dot st
2014-04-10 10:20 ` ebotcazou at gcc dot gnu.org
2014-04-11 16:28 ` gnugcc at marino dot st
2014-04-17 9:14 ` gnugcc at marino dot st
2014-04-17 10:54 ` ebotcazou at gcc dot gnu.org
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-60411-4-NqXx5Kfme3@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).