install: Streamline the hppa*-hp-hpux* section
Checks
Context |
Check |
Description |
linaro-tcwg-bot/tcwg_gcc_build--master-arm |
success
|
Testing passed
|
linaro-tcwg-bot/tcwg_gcc_build--master-aarch64 |
success
|
Testing passed
|
linaro-tcwg-bot/tcwg_gcc_check--master-aarch64 |
success
|
Testing passed
|
Commit Message
John, Jeff,
I suggest to streamline the hppa*-hp-hpux* installation instructions as
follows. Okay?
In fact in the following sections there is even more, and more specific
material, which would be great could you have a look at and help trim.
Gerald
From 52149282c3a77ccda6385f06f36323c71b26491a Mon Sep 17 00:00:00 2001
From: Gerald Pfeifer <gerald@pfeifer.com>
Date: Sun, 17 Dec 2023 09:33:40 +0800
Subject: [PATCH] install: Streamline the hppa*-hp-hpux* section
gcc:
PR target/69374
* doc/install.texi (Specific) <hppa*-hp-hpux*>: Remove a note on
GCC 4.3.
Remove details on how the HP assembler, which we document as not
working, breaks.
---
gcc/doc/install.texi | 17 -----------------
1 file changed, 17 deletions(-)
Comments
Hi Gerald,
I have one comment. The only target currently supported is hppa64-hp-hpux11*.
While gas is required, only the HP ld works.
Otherwise, the change looks fine.
Dave
On 2023-12-16 8:35 p.m., Gerald Pfeifer wrote:
> John, Jeff,
>
> I suggest to streamline the hppa*-hp-hpux* installation instructions as
> follows. Okay?
>
> In fact in the following sections there is even more, and more specific
> material, which would be great could you have a look at and help trim.
>
> Gerald
>
>
>
> >From 52149282c3a77ccda6385f06f36323c71b26491a Mon Sep 17 00:00:00 2001
> From: Gerald Pfeifer <gerald@pfeifer.com>
> Date: Sun, 17 Dec 2023 09:33:40 +0800
> Subject: [PATCH] install: Streamline the hppa*-hp-hpux* section
>
> gcc:
>
> PR target/69374
> * doc/install.texi (Specific) <hppa*-hp-hpux*>: Remove a note on
> GCC 4.3.
> Remove details on how the HP assembler, which we document as not
> working, breaks.
> ---
> gcc/doc/install.texi | 17 -----------------
> 1 file changed, 17 deletions(-)
>
> diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
> index 5ec81098d47..70d46feabf6 100644
> --- a/gcc/doc/install.texi
> +++ b/gcc/doc/install.texi
> @@ -4121,8 +4121,6 @@ longer a multiple of 2 bytes.
> @end html
> @anchor{hppa-hp-hpux}
> @heading hppa*-hp-hpux*
> -Support for HP-UX version 9 and older was discontinued in GCC 3.4.
> -
> We require using gas/binutils on all hppa platforms. Version 2.19 or
> later is recommended.
>
> @@ -4130,21 +4128,6 @@ It may be helpful to configure GCC with the
> @uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
> @option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
>
> -The HP assembler should not be used with GCC. It is rarely tested and may
> -not work. It shouldn't be used with any languages other than C due to its
> -many limitations.
> -
> -Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
> -format which GCC does not know about). It also inserts timestamps
> -into each object file it creates, causing the 3-stage comparison test to
> -fail during a bootstrap. You should be able to continue by saying
> -@samp{make all-host all-target} after getting the failure from @samp{make}.
> -
> -Various GCC features are not supported. For example, it does not support weak
> -symbols or alias definitions. As a result, explicit template instantiations
> -are required when using C++. This makes it difficult if not impossible to
> -build many C++ applications.
> -
> There are two default scheduling models for instructions. These are
> PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
> architecture specified for the target machine when configuring.
On Sat, 16 Dec 2023, John David Anglin wrote:
> I have one comment. The only target currently supported is
> hppa64-hp-hpux11*. While gas is required, only the HP ld works.
>
> Otherwise, the change looks fine.
Thank you, Dave!
I updated the patch accordingly, referring to gas (not gas/binutils) and
being explicit around the flavor of ld to use, and pushed it.
Any further comments or suggestions, let me know.
Gerald
commit da70c5b17123b7c81155ef03fb4591b71a681344
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date: Sun Dec 17 15:13:39 2023 +0800
install: Streamline the hppa*-hp-hpux* section
gcc:
PR target/69374
* doc/install.texi (Specific) <hppa*-hp-hpux*>: Remove a note on
GCC 4.3.
Remove details on how the HP assembler, which we document as not
working, breaks.
<hppa*-hp-hpux11>: Note that only the HP linker is supported.
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 5ec81098d47..84d8834a9b5 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -4121,30 +4121,13 @@ longer a multiple of 2 bytes.
@end html
@anchor{hppa-hp-hpux}
@heading hppa*-hp-hpux*
-Support for HP-UX version 9 and older was discontinued in GCC 3.4.
-
-We require using gas/binutils on all hppa platforms. Version 2.19 or
+We require using gas on all hppa platforms. Version 2.19 or
later is recommended.
It may be helpful to configure GCC with the
@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
@option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
-The HP assembler should not be used with GCC. It is rarely tested and may
-not work. It shouldn't be used with any languages other than C due to its
-many limitations.
-
-Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
-format which GCC does not know about). It also inserts timestamps
-into each object file it creates, causing the 3-stage comparison test to
-fail during a bootstrap. You should be able to continue by saying
-@samp{make all-host all-target} after getting the failure from @samp{make}.
-
-Various GCC features are not supported. For example, it does not support weak
-symbols or alias definitions. As a result, explicit template instantiations
-are required when using C++. This makes it difficult if not impossible to
-build many C++ applications.
-
There are two default scheduling models for instructions. These are
PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
architecture specified for the target machine when configuring.
@@ -4269,9 +4252,7 @@ options, including program core dumps. Binutils 2.14 corrects a
problem on the 64-bit port resulting from HP's non-standard use of
the .init and .fini sections for array initializers and finalizers.
-Although the HP and GNU linkers are both supported for the
-@samp{hppa64-hp-hpux11*} target, it is strongly recommended that the
-HP linker be used for link editing on this target.
+Only the HP linker is supported for the @samp{hppa64-hp-hpux11*} target.
At this time, the GNU linker does not support the creation of long
branch stubs. As a result, it cannot successfully link binaries
@@ -4121,8 +4121,6 @@ longer a multiple of 2 bytes.
@end html
@anchor{hppa-hp-hpux}
@heading hppa*-hp-hpux*
-Support for HP-UX version 9 and older was discontinued in GCC 3.4.
-
We require using gas/binutils on all hppa platforms. Version 2.19 or
later is recommended.
@@ -4130,21 +4128,6 @@ It may be helpful to configure GCC with the
@uref{./configure.html#with-gnu-as,,@option{--with-gnu-as}} and
@option{--with-as=@dots{}} options to ensure that GCC can find GAS@.
-The HP assembler should not be used with GCC. It is rarely tested and may
-not work. It shouldn't be used with any languages other than C due to its
-many limitations.
-
-Specifically, @option{-g} does not work (HP-UX uses a peculiar debugging
-format which GCC does not know about). It also inserts timestamps
-into each object file it creates, causing the 3-stage comparison test to
-fail during a bootstrap. You should be able to continue by saying
-@samp{make all-host all-target} after getting the failure from @samp{make}.
-
-Various GCC features are not supported. For example, it does not support weak
-symbols or alias definitions. As a result, explicit template instantiations
-are required when using C++. This makes it difficult if not impossible to
-build many C++ applications.
-
There are two default scheduling models for instructions. These are
PROCESSOR_7100LC and PROCESSOR_8000. They are selected from the pa-risc
architecture specified for the target machine when configuring.