Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Luis Alves <ljalvs@gmail.com>
Cc: Daniel Palmer <danieruru@gmail.com>, linux-m68k@vger.kernel.org
Subject: Re: Getting stuck during boot on a 68VZ328 (DragonBallVZ).
Date: Wed, 2 Apr 2014 23:02:16 +1100 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.00.1404022244160.18569@nippy.intranet> (raw)
In-Reply-To: <CAGj5WxBpHJwH5sgE_kmOGL+xq-kLNBTuab_0mZw7gy-XuEYifQ@mail.gmail.com>


On Wed, 2 Apr 2014, Luis Alves wrote:

> Hi Daniel,
> 
> Nice work.
> I remember that I managed to get gcc 4.7.2 working (I had to patch a
> few files in gcc due to abi changes).
> ...
> > Here is the bug: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386

Would you mind revisiting the bug report to attach the patch or add a 
comment with a link to the patch submission?

The last thing you wrote in the bug report suggests that strict alignment 
isn't sufficient to fix the problem or else gcc-4.6 contains some sort of 
regression that caused Linux to log "BUG", which is a bit confusing.

Finn

  parent reply	other threads:[~2014-04-02 12:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 17:58 Getting stuck during boot on a 68VZ328 (DragonBallVZ) Daniel Palmer
2014-03-28  6:38 ` Daniel Palmer
2014-03-28 10:17   ` Luis Alves
2014-04-02  1:42   ` Daniel Palmer
2014-04-02  5:06     ` Finn Thain
2014-04-02  5:35       ` Daniel Palmer
2014-04-02 10:47         ` Luis Alves
2014-04-02 11:33           ` Daniel Palmer
2014-04-02 12:02           ` Finn Thain [this message]
2014-04-02 12:31           ` Greg Ungerer
2014-04-02 12:26     ` Greg Ungerer
2014-04-02 13:19       ` Daniel Palmer
2014-04-03 12:46         ` Greg Ungerer

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=alpine.LNX.2.00.1404022244160.18569@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=danieruru@gmail.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=ljalvs@gmail.com \
    /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