On Fri, Oct 16, 2026 at 06:53:14PM -0400, Brad Smith wrote:
> On 2026-10-16 6:11 p.m., Jeremie Courreges-Anglas wrote:
> > On Fri, Oct 16, 2026 at 05:51:11PM -0400, Brad Smith wrote:
> > > On 2026-10-16 5:38 p.m., Jeremie Courreges-Anglas wrote:
> > > > +cc $MAINTAINER
> > > >
> > > > On Fri, Oct 16, 2026 at 04:19:26PM -0400, Brad Smith wrote:
> > > > > On 2026-10-16 5:29 a.m., Kirill A. Korinsky wrote:
> > > > > > On Fri, 16 Oct 2026 09:27:30 +0200,
> > > > > > Brad Smith <[email protected]> wrote:
> > > > > > > Some fixes for bootgcc..
> > > > > > >
> > > > > > > - Sync the hppa bits over from lang/gcc/8 to bootgcc
> > > > > > > - Fix ONLY_FOR_ARCHS no point for m88k
> > > > > > >
> > > > > > >
> > > > > > I wonder why have you drop support of m88k from bootgcc?
> > > > > There is no m88k support.
> > > > You mean it doesn't have patches for OpenBSD/m88k, but it has support
> > > > for m88k on other systems.
> > > No, I don't mean that at all.
> > Then say what you mean, stop forcing people to ask again and take
> > guesses. This is fucking tiresome, it wastes time and generates
> > mistakes.
> >
> > I see files used for m88k support in lang/bootgcc, even though the
> > target seems marked as obsolete. What leads you to say that there is
> > NO m88k support?
>
> I did say what I mean. There hasn't been a backend upstream for 23 years. It
> was
> removed before GCC 4. There are no files in the port referring to 88k.
>
> https://github.com/gcc-mirror/gcc/commit/7c942e1747c951401736c0cfc144bc307d728b6c
That is helpful.
> $ grep 88 *
> patch-Makefile_in:@@ -58884,7 +58883,7 @@ configure-target-rda:
> patch-gcc_config_alpha_alpha_cc:@@ -8480,6 +8488,8 @@ alpha_expand_prologue
> (void)
> patch-gcc_config_gcc:@@ -3817,6 +3880,12 @@ case ${target} in
> patch-gcc_config_sparc_sparc_cc:@@ -2287,6 +2288,16 @@
> can_use_mov_pic_label_ref (rtx label)
> patch-gcc_d_d-target_cc:@@ -488,7 +488,7 @@ tree
> patch-gcc_opts_cc:@@ -2889,6 +2894,11 @@ common_handle_option (struct
> gcc_options *opts,
> patch-gcc_tree-ssa-loop-ivopts_cc:57efa2046671372c1e17cec6100e23716af688b9
> patch-libphobos_libdruntime_config_riscv64_switchcontext_S:+ fsd fs11,
> 88(sp)
> patch-libphobos_libdruntime_config_riscv64_switchcontext_S:+ fld fs11,
> 88(sp)
> patch-libphobos_libdruntime_config_sparc64_switchcontext_S:+ std %f52,
> [%g1 + RSA + 88]
> patch-libphobos_libdruntime_config_sparc64_switchcontext_S:+ ldd [%g1
> + RSA + 88], %f52
> patch-libstdc++-v3_src_c++11_debug_cc:@@ -880,7 +880,7 @@ namespace
>
> Where?
There are files that mention m88k in the *tarball*. But indeed, no
gcc/config/m88k etc - and no m88k patch in the port, as already
stated.
Now that I have a clear reason, I'll drop m88k from ONLY_FOR_ARCHS
when committing.
Thanks,
--
jca
