From: Peter Schauer <Peter.Schauer@mytum.de>
To: cagney@gnu.org (Andrew Cagney)
Cc: kevinb@redhat.com, brobecker@gnat.com, gdb@sources.redhat.com
Subject: Re: AIX and xm-aix.h
Date: Sun, 08 Aug 2004 07:35:00 -0000 [thread overview]
Message-ID: <200408080735.i787ZNto002075@licht.localdomain> (raw)
In-Reply-To: <41152ACC.9080308@gnu.org> from "Andrew Cagney" at Aug 07, 2004 03:17:32 PM
I have very limited AIX resources nowadays, only an AIX 4.3 system with gcc,
no native compiler.
On this system I almost emptied xm.h, only
#define FIVE_ARG_PTRACE
had to be there, otherwise GDB doesn't compile.
It should be possible to handle this via some autoconf logic though.
Testsuite results were unchanged with the almost empty xm.h
Visual inspection of the xm files turned up only two more things:
- #pragma alloca might be needed for IBM xlc. It might be sufficient to
include malloc.h for an alloca definition for IBM xlc, according to some
old notes of mine.
- We will loose the SIGWINCH_HANDLER. Not a big deal in my opinion.
Maybe it even works without it on current AIX versions. And somebody can
always reimplement it more cleanly if it is needed desperately.
- USE_O_NOCTTY might be needed for some other AIX versions, but maybe only
for the old AIX 3.2.5.
HTH,
> Peter,
>
> GDB's currently expunging all the xm-*.h files from it's configuration
> (instead relying strictly on autoconf). For most systems this is
> straight forward (the xm files were empty / redundant). Unfortunatly,
> for AIX, it looks like there could be problems.
>
> Can we try removing the xm files and identify / fix any problems?
>
> It would be good to see this task finally closed.
>
> Andrew
>
--
Peter Schauer Peter.Schauer@mytum.de
prev parent reply other threads:[~2004-08-08 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 19:17 Andrew Cagney
2004-08-08 4:21 ` Joel Brobecker
2004-08-08 7:35 ` Peter Schauer [this message]
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=200408080735.i787ZNto002075@licht.localdomain \
--to=peter.schauer@mytum.de \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kevinb@redhat.com \
/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