[Bug target/25496] [m68k] Compiled Code Segfaults

2006-05-08 Thread kazu at gcc dot gnu dot org
--- Comment #5 from kazu at gcc dot gnu dot org 2006-05-08 16:21 --- Closed as the submitter agrees. -- kazu at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/25496] [m68k] Compiled Code Segfaults

2006-05-08 Thread stephen at marenka dot net
--- Comment #4 from stephen at marenka dot net 2006-05-08 15:39 --- Subject: Re: [m68k] Compiled Code Segfaults On Mon, May 08, 2006 at 03:26:13PM -, kazu at gcc dot gnu dot org wrote: > Can we close this PR now? Can't say I like the segfault much, but it doesn't seem to show up

[Bug target/25496] [m68k] Compiled Code Segfaults

2006-05-08 Thread kazu at gcc dot gnu dot org
--- Comment #3 from kazu at gcc dot gnu dot org 2006-05-08 15:26 --- Can we close this PR now? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25496

[Bug target/25496] [m68k] Compiled Code Segfaults

2005-12-19 Thread stephen at marenka dot net
--- Comment #2 from stephen at marenka dot net 2005-12-19 21:21 --- It does not. I'll report the aliasing violation back to the csound maintainer. I wonder why it's only a problem on m68k. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25496

[Bug target/25496] [m68k] Compiled Code Segfaults

2005-12-19 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-12-19 21:14 --- *(long *)benchar You are violating C aliasing rules as you are acessing a char array as a long (yes this is an aliasing violation, the opposite is not an aliasing violation that is acessing a long as a char is not a