public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@sysam.it>
To: Finn Thain <fthain@telegraphics.com.au>,
	debian-68k@lists.debian.org, linux-m68k@vger.kernel.org
Subject: Re: gcc-4.6.3, was Re: Debian on mac68k
Date: Mon, 7 Nov 2016 10:35:06 +0100	[thread overview]
Message-ID: <5873dbec-38c0-7f7f-4a6b-68c5deb546be@sysam.it> (raw)
In-Reply-To: <alpine.LNX.2.00.1611052134280.2870@nippy.intranet>

Hi Finn,

On 06/11/2016 03:03, Finn Thain wrote:
>
> Has anyone else tried the m68k cross-compiler from kernel.org and observed
> strange behaviour from the binaries it produces?
>
> I used that cross-compiler (the i686 one) to build the kernel seen booting
> below. The resulting binary consistently crashes two different systems (LC
> III and LC 475), both during kernel startup. These two machines use
> different drivers and have different failure modes, but the failures are
> completely repeatable. The failures went away when I reverted to my usual
> (patched) gcc-4.4.6.
>
> Perhaps gcc-4.6.3 is more strict than gcc-4.4, in such a way that would
> affect code generation, when presented with incorrect or undefined code?
> Are there any warnings that could be enabled to discover that code?
>
> Is there some way to run the GCC test suite against this cross-compiler?
>

I also observed issues with some kernel.org toolchains, at least for coldfire
the 4.9.x was producing some wrong opcode, due to incorrect gcc libs used
over linking.

Maybe you can try some toolchains i prepared, they are the kernel.org with
some packaging adjustments done by me. Let me know in case if they work
for you.


http://sysam.it/toolchains.html

Regards,
Angelo Durgehello

  parent reply	other threads:[~2016-11-07  9:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <574C132F.3070404@abbuc.de>
     [not found] ` <574C15C2.90908@abbuc.de>
     [not found]   ` <ec5ded9d-b3c0-0bba-65b7-1e4d2cc063a2@physik.fu-berlin.de>
     [not found]     ` <574C1792.4030403@abbuc.de>
     [not found]       ` <57557722.5040808@yahoo.com>
     [not found]         ` <alpine.LNX.2.00.1610251358330.443@nippy.intranet>
     [not found]           ` <5810FA8D.4060702@yahoo.com>
     [not found]             ` <58114F74.40408@yahoo.com>
     [not found]               ` <alpine.LNX.2.00.1610271244020.21780@nippy.intranet>
     [not found]                 ` <5811F96F.3090602@yahoo.com>
     [not found]                   ` <58121D46.8060506@yahoo.com>
2016-11-06  2:03                     ` gcc-4.6.3, was Re: Debian on mac68k Finn Thain
2016-11-06  9:42                       ` John Paul Adrian Glaubitz
2016-11-06 22:22                         ` Finn Thain
2016-11-06 22:33                           ` John Paul Adrian Glaubitz
2016-11-07  0:37                             ` Finn Thain
2016-11-09  6:50                           ` Michael Schmitz
2016-11-09  7:08                             ` Finn Thain
2016-11-09  8:39                               ` Geert Uytterhoeven
2016-11-21  9:10                               ` Mac emulation, was Re: gcc-4.6.3 Finn Thain
2016-11-09 10:14                             ` gcc-4.6.3, was Re: Debian on mac68k John Paul Adrian Glaubitz
2016-11-16 12:43                             ` Kaj-Michael Lang
2016-11-16 13:23                               ` John Paul Adrian Glaubitz
2016-11-16 22:26                               ` sun3 emulation, was Re: gcc-4.6.3 Finn Thain
2016-11-22 15:46                                 ` Sam Creasey
2016-11-07  9:35                       ` Angelo Dureghello [this message]
2016-11-08  9:01                         ` gcc-4.6.3, was Re: Debian on mac68k Finn Thain
2016-11-08  9:05                           ` John Paul Adrian Glaubitz
2016-11-08 23:06                             ` Finn Thain
2016-11-09 10:24                               ` John Paul Adrian Glaubitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5873dbec-38c0-7f7f-4a6b-68c5deb546be@sysam.it \
    --to=angelo@sysam.it \
    --cc=debian-68k@lists.debian.org \
    --cc=fthain@telegraphics.com.au \
    --cc=linux-m68k@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox