Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Martin Michlmayr <tbm@cyrius.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: David Daney <ddaney@avtrex.com>,
	MIPS Linux List <linux-mips@linux-mips.org>
Subject: Re: Gcc 4.2.2 broken for kernel builds
Date: Fri, 12 Oct 2007 22:33:54 +0200	[thread overview]
Message-ID: <20071012203354.GA18618@deprecation.cyrius.com> (raw)
In-Reply-To: <20071012191446.GK3163@deprecation.cyrius.com>

* Martin Michlmayr <tbm@cyrius.com> [2007-10-12 21:14]:
> Okay, I can see it.  I'll submit a testcase.

I submitted the following:

(sid)335:tbm@swarm: ~] gcc-4.2 -c -march=mips32r2 -O2 pr33755.c
(sid)336:tbm@swarm: ~] ld -m elf32ltsmip -r pr33755.o
ld: pr33755.o: Can't find matching LO16 reloc against `$LC0' for R_MIPS_GOT16 at 0x521490 in section `.text'
(sid)337:tbm@swarm: ~] cat pr33755.c
struct mtd_blktrans_ops
{
  int (*readsect) (void);
  int exiting;
};
static void do_blktrans_request (struct mtd_blktrans_ops *tr, long flags)
{
  switch (flags & 1)
    {
    case 0:
      if (tr->readsect ())
        return;
    case 1:
      return;
    default:
      printk ("foo\n");
    }
}
mtd_blktrans_thread (struct mtd_blktrans_ops *tr)
{
  long flags;
  while (!tr->exiting)
      do_blktrans_request (tr, flags);
}

-- 
Martin Michlmayr
http://www.cyrius.com/

  parent reply	other threads:[~2007-10-12 20:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 17:22 Gcc 4.2.2 broken for kernel builds Ralf Baechle
2007-10-12 17:48 ` David Daney
2007-10-12 17:53   ` Ralf Baechle
2007-10-12 18:33     ` David Daney
2007-10-12 18:49       ` Ralf Baechle
2007-10-12 19:14         ` Martin Michlmayr
2007-10-12 19:16           ` Ralf Baechle
2007-10-13 10:51             ` Richard Sandiford
2007-10-15 14:59               ` Maciej W. Rozycki
2007-10-15 16:19                 ` Richard Sandiford
2007-10-24 19:46             ` Martin Michlmayr
2007-10-12 20:33           ` Martin Michlmayr [this message]
2007-10-12 18:45     ` Martin Michlmayr
2007-10-12 22:42 ` David Daney

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=20071012203354.GA18618@deprecation.cyrius.com \
    --to=tbm@cyrius.com \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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