public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] m68k: restore bootstrap
@ 2024-02-18  9:18 Mikael Pettersson
  2024-02-18 15:42 ` Jeff Law
  0 siblings, 1 reply; 3+ messages in thread
From: Mikael Pettersson @ 2024-02-18  9:18 UTC (permalink / raw)
  To: gcc-patches; +Cc: Mikael Pettersson

m68k fails to bootstrap since -ffold-mem-offsets was introduced,
in what looks like wrong-code during stage2.

To restore bootstrap this disables -ffold-mem-offsets on m68k.
It's not ideal, but better than keeping bootstraps broken until
the root cause is debugged and fixed.

Tested with a bootstrap and regression test run on m68k-linux-gnu.

Ok for master? (I'll need help getting it committed.)

gcc/
	PR target/113357
	* config/m68k/m68k.cc (m68k_option_override): Disable
	-ffold-mem-offsets.  Fix typo in comment.
---
 gcc/config/m68k/m68k.cc | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gcc/config/m68k/m68k.cc b/gcc/config/m68k/m68k.cc
index b1c9238949f..700f8151286 100644
--- a/gcc/config/m68k/m68k.cc
+++ b/gcc/config/m68k/m68k.cc
@@ -587,7 +587,7 @@ m68k_option_override (void)
 	      : (m68k_cpu_flags & FL_COLDFIRE) != 0 ? FPUTYPE_COLDFIRE
 	      : FPUTYPE_68881);
 
-  /* Sanity check to ensure that msep-data and mid-sahred-library are not
+  /* Sanity check to ensure that msep-data and mid-shared-library are not
    * both specified together.  Doing so simply doesn't make sense.
    */
   if (TARGET_SEP_DATA && TARGET_ID_SHARED_LIBRARY)
@@ -716,6 +716,9 @@ m68k_option_override (void)
       else
 	m68k_sched_mac = MAC_NO;
     }
+
+  /* -ffold-mem-offsets doesn't work for m68k (PR113357).  */
+  flag_fold_mem_offsets = 0;
 }
 
 /* Implement TARGET_OVERRIDE_OPTIONS_AFTER_CHANGE.  */
-- 
2.43.0


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] m68k: restore bootstrap
  2024-02-18  9:18 [PATCH] m68k: restore bootstrap Mikael Pettersson
@ 2024-02-18 15:42 ` Jeff Law
  2024-02-18 23:36   ` Oleg Endo
  0 siblings, 1 reply; 3+ messages in thread
From: Jeff Law @ 2024-02-18 15:42 UTC (permalink / raw)
  To: gcc-patches



On 2/18/24 02:18, Mikael Pettersson wrote:
> m68k fails to bootstrap since -ffold-mem-offsets was introduced,
> in what looks like wrong-code during stage2.
> 
> To restore bootstrap this disables -ffold-mem-offsets on m68k.
> It's not ideal, but better than keeping bootstraps broken until
> the root cause is debugged and fixed.
> 
> Tested with a bootstrap and regression test run on m68k-linux-gnu.
> 
> Ok for master? (I'll need help getting it committed.)
> 
> gcc/
> 	PR target/113357
> 	* config/m68k/m68k.cc (m68k_option_override): Disable
> 	-ffold-mem-offsets.  Fix typo in comment.
Definitely not OK.    This needs to be debugged further, just disabling 
the pass is not the right solution here.

It is also worth noting I'm bootstrapping and regression testing the 
m68k weekly.

jeff


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] m68k: restore bootstrap
  2024-02-18 15:42 ` Jeff Law
@ 2024-02-18 23:36   ` Oleg Endo
  0 siblings, 0 replies; 3+ messages in thread
From: Oleg Endo @ 2024-02-18 23:36 UTC (permalink / raw)
  To: Jeff Law, gcc-patches

On Sun, 2024-02-18 at 08:42 -0700, Jeff Law wrote:
> 
> On 2/18/24 02:18, Mikael Pettersson wrote:
> > m68k fails to bootstrap since -ffold-mem-offsets was introduced,
> > in what looks like wrong-code during stage2.
> > 
> > To restore bootstrap this disables -ffold-mem-offsets on m68k.
> > It's not ideal, but better than keeping bootstraps broken until
> > the root cause is debugged and fixed.
> > 
> > Tested with a bootstrap and regression test run on m68k-linux-gnu.
> > 
> > Ok for master? (I'll need help getting it committed.)
> > 
> > gcc/
> > 	PR target/113357
> > 	* config/m68k/m68k.cc (m68k_option_override): Disable
> > 	-ffold-mem-offsets.  Fix typo in comment.
> Definitely not OK.    This needs to be debugged further, just disabling 
> the pass is not the right solution here.
> 
> It is also worth noting I'm bootstrapping and regression testing the 
> m68k weekly.
> 
> 

Jeff, could you please consider sharing your test setup so that others can
reproduce it as well?

I'd be really better if more people had access to a unified test setup and
methodology.

Best regards,
Oleg Endo

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-02-18 23:36 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-02-18  9:18 [PATCH] m68k: restore bootstrap Mikael Pettersson
2024-02-18 15:42 ` Jeff Law
2024-02-18 23:36   ` Oleg Endo

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).