public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Randy Galbraith <randy.galbraith@gmail.com>
Cc: David Edelsohn <dje.gcc@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Building gcc 4.9.2 on AIX 7.1
Date: Tue, 13 Jun 2023 13:42:38 +0300	[thread overview]
Message-ID: <CAH6eHdTJrJeXG-Apy9akugtqc15uBsk-UWg-hF76BjZEmRwbLw@mail.gmail.com> (raw)
In-Reply-To: <CA+DxmavqcZALr0geF4UhC1v7hxmauYmtyVC8gfFqm4wD69kN1w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2342 bytes --]

On Tue, 13 Jun 2023, 13:36 Randy Galbraith via Gcc-help, <
gcc-help@gcc.gnu.org> wrote:

> On Mon, Jun 12, 2023 at 6:50 PM David Edelsohn <dje.gcc@gmail.com> wrote:
>
> > >>> Randy Galbraith wrote:
> >
> > > We have a need to match gcc version on Red Hat GNU/Linux 7. I am
> looking
> > > forward to newer GCC once Red Hat is upgraded. However, that will
> likely
> > > break our build. We elevate every warning in gcc to error status that
> > stops
> > > the building. Thus we need to plan for that. At the moment I just need
> to
> > > support the AIX 7.2 upgrade. Ironically had our port to GNU/Linux been
> > > completed this would not be an issue. Cheers, -Randy
> >
> > Red Hat provides newer releases of GCC through the GCC Toolset
> > package, but that may be limited to RHEL 8.  RHEL 7 is quite old.
> >
> > Does your AIX 7.2 system have all of the latest Technology Levels
> > (TLs) and Service Packs (SPs) installed? There have been many
> > assembler and linker fixes.
> >
> > If you still have GCC 4.9.2 from the AIX 7.1 system, you should be
> > able to continue to use it.  You can rebuild the "fixed" headers
> > without rebuilding the entire compiler.  I don't believe that anyone
> > has tried bootstrapping GCC with XLC in a very long time.
> >
> > GCC builds and works with AIX Assembler and AIX Linker.  Until
> > recently, GNU Assembler and GNU Linker were out of date on AIX 7.x and
> > produced corrupted object files. The latest GNU Binutils functions.
> > It might be better to ensure that the AIX tools are used (AIX as, ld,
> > ar).
> >
> > GCC 4.9 is very old. I don't have any intuition about why GCC (without
> > any optimization) would generate unusual code for ferror().  Again, I
> > would ensure that you are not using the GNU Assembler for your
> > bootstrap.
> >
> > Thanks, David
> >
>
> I am trying to land a new GCC compiler to address the break related to
> fixed headers. If these could be rebuilt without having to land a new
> compiler I would be most interested in the steps to do that! Any advice on
> where to start with that? Cheers, -Randy
>


See https://gcc.gnu.org/onlinedocs/gcc/Fixed-Headers.html which describes
the mkheaders script. That is installed as part of the GCC installation,
and running it will update the fixed headers.

  reply	other threads:[~2023-06-13 10:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 22:50 David Edelsohn
2023-06-13 10:29 ` Randy Galbraith
2023-06-13 10:42   ` Jonathan Wakely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-11 12:26 Randy Galbraith
2023-06-11 15:27 ` Tom Kacvinsky
2023-06-11 16:27   ` Tom Kacvinsky
2023-06-11 19:04     ` Randy Galbraith
2023-06-11 21:04       ` Jonathan Wakely
2023-06-11 22:37         ` Randy Galbraith
2023-06-12 15:54           ` Randy Galbraith
2023-06-13  7:38             ` Christer Solskogen
2023-06-13 10:35               ` Randy Galbraith
2023-06-15 16:44                 ` Randy Galbraith
2023-06-15 22:05                   ` Jonathan Wakely
2023-06-16 19:46                     ` Randy Galbraith
2023-06-11 18:31 ` Kai Ruottu
2023-06-11 22:23   ` Randy Galbraith

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=CAH6eHdTJrJeXG-Apy9akugtqc15uBsk-UWg-hF76BjZEmRwbLw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=randy.galbraith@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).