Bug#711558: PR52306 (was Re: Bug#711558: gcc-4.8: [m68k] patch set 2)

2013-09-01 Thread Thorsten Glaser
Matthias Klose dixit:

I think, setting the flag for the option to 0 as the default, and
applying this for m68k only would be the second best option, provided

Right…

that you cannot find out how to implement Mikael's suggestion.

… but I think I know, generally, how to do that.
(Have been dealing with GCC’s ever-changing options subsystem
since 2.x times, in various BSDs mostly.)

Just ENOTIME right now. I’ll get back to you all.

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#711558: PR52306 (was Re: Bug#711558: gcc-4.8: [m68k] patch set 2)

2013-08-28 Thread Matthias Klose
Am 23.08.2013 00:26, schrieb Thorsten Glaser:
 Matthias Klose dixit:
 
 yes, I do reject this.
 
 I see. Would you please…
 
 “for the time being”? If so, would you accept a patch
 that just disables -fauto-inc-dec on m68k *always*,
 even in the cases where it doesn’t ICE? (one-liner)
 
 answer whether this would be considerable? (Untested,
 but should have the desired effect, right Mikael?)
 
 --- a/src/gcc/common.opt
 +++ b/src/gcc/common.opt
 @@ -858,7 +858,7 @@ Common Report Var(flag_asynchronous_unwi
  Generate unwind tables that are exact at each instruction boundary
  
  fauto-inc-dec
 -Common Report Var(flag_auto_inc_dec) Init(1)
 +Common Report Var(flag_auto_inc_dec) Init(0)
  Generate auto-inc/dec instructions
  
  ; -fcheck-bounds causes gcc to generate array bounds checks.
 
 Or maybe this one (although it’s got the malus that it can’t
 be re-enabled for testing):
 
 --- a/src/gcc/config/m68k/m68k.c
 +++ b/src/gcc/config/m68k/m68k.c
 @@ -663,6 +663,8 @@ m68k_override_options_after_change (void
flag_schedule_insns_after_reload = 0;
flag_modulo_sched = 0;
  }
 +  /* PR52306 */
 +  flag_auto_inc_dec = 0;
  }
  
  /* Generate a macro of the form __mPREFIX_cpu_NAME, where PREFIX is the
 
 not many thanks for trying to sneak in this into the
 Debian package.
 
 I’m just forwarding what we use in production. This is
 really necessary right now to work around bugs with the
 GNU Chagrin Collection.
 
 Apparently just always disabling optimisation is the
 way, not just when it is problematic…

I think, setting the flag for the option to 0 as the default, and applying this
for m68k only would be the second best option, provided that you cannot find out
how to implement Mikael's suggestion.

  Matthias


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#711558: PR52306 (was Re: Bug#711558: gcc-4.8: [m68k] patch set 2)

2013-08-23 Thread Mikael Pettersson
On Thu, 22 Aug 2013 22:26:51 + (UTC), Thorsten Glaser t...@mirbsd.de 
wrote:
 Matthias Klose dixit:
 
 yes, I do reject this.
 
 I see. Would you please=E2=80=A6
 
  =E2=80=9Cfor the time being=E2=80=9D? If so, would you accept a patch
  that just disables -fauto-inc-dec on m68k *always*,
  even in the cases where it doesn=E2=80=99t ICE? (one-liner)
 
 answer whether this would be considerable? (Untested,
 but should have the desired effect, right Mikael?)
 
 --- a/src/gcc/common.opt
 +++ b/src/gcc/common.opt
 @@ -858,7 +858,7 @@ Common Report Var(flag_asynchronous_unwi
  Generate unwind tables that are exact at each instruction boundary
 =20
  fauto-inc-dec
 -Common Report Var(flag_auto_inc_dec) Init(1)
 +Common Report Var(flag_auto_inc_dec) Init(0)
  Generate auto-inc/dec instructions
 =20
  ; -fcheck-bounds causes gcc to generate array bounds checks.
 
 Or maybe this one (although it=E2=80=99s got the malus that it can=E2=80=99=
 t
 be re-enabled for testing):
 
 --- a/src/gcc/config/m68k/m68k.c
 +++ b/src/gcc/config/m68k/m68k.c
 @@ -663,6 +663,8 @@ m68k_override_options_after_change (void
flag_schedule_insns_after_reload =3D 0;
flag_modulo_sched =3D 0;
  }
 +  /* PR52306 */
 +  flag_auto_inc_dec =3D 0;
  }
 =20
  /* Generate a macro of the form __mPREFIX_cpu_NAME, where PREFIX is the

Tweaking the option so that it defaults to OFF for m68k, but still can be
enabled, would be preferable.  I haven't looked at how to achieve that in
gcc's options machinery.

/Mikael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#711558: PR52306 (was Re: Bug#711558: gcc-4.8: [m68k] patch set 2)

2013-08-22 Thread Thorsten Glaser
Matthias Klose dixit:

yes, I do reject this.

I see. Would you please…

 “for the time being”? If so, would you accept a patch
 that just disables -fauto-inc-dec on m68k *always*,
 even in the cases where it doesn’t ICE? (one-liner)

answer whether this would be considerable? (Untested,
but should have the desired effect, right Mikael?)

--- a/src/gcc/common.opt
+++ b/src/gcc/common.opt
@@ -858,7 +858,7 @@ Common Report Var(flag_asynchronous_unwi
 Generate unwind tables that are exact at each instruction boundary
 
 fauto-inc-dec
-Common Report Var(flag_auto_inc_dec) Init(1)
+Common Report Var(flag_auto_inc_dec) Init(0)
 Generate auto-inc/dec instructions
 
 ; -fcheck-bounds causes gcc to generate array bounds checks.

Or maybe this one (although it’s got the malus that it can’t
be re-enabled for testing):

--- a/src/gcc/config/m68k/m68k.c
+++ b/src/gcc/config/m68k/m68k.c
@@ -663,6 +663,8 @@ m68k_override_options_after_change (void
   flag_schedule_insns_after_reload = 0;
   flag_modulo_sched = 0;
 }
+  /* PR52306 */
+  flag_auto_inc_dec = 0;
 }
 
 /* Generate a macro of the form __mPREFIX_cpu_NAME, where PREFIX is the

not many thanks for trying to sneak in this into the
Debian package.

I’m just forwarding what we use in production. This is
really necessary right now to work around bugs with the
GNU Chagrin Collection.

Apparently just always disabling optimisation is the
way, not just when it is problematic…

bye,
//mirabilos
-- 
In traditional syntax ' is ignored, but in c99 everything between two ' is
handled as character constant.  Therefore you cannot use ' in a preproces-
sing file in c99 mode.  -- Ragge
No faith left in ISO C99, undefined behaviour, etc.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org