public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sergey Anosov <aserg2004@list.ru>
To: gcc@gcc.gnu.org
Subject: mips64 gcc 3.3.6 problem
Date: Wed, 19 Aug 2009 11:53:00 -0000	[thread overview]
Message-ID: <E1MdhYW-0005WQ-00.aserg2004-list-ru@f143.mail.ru> (raw)

Hi all!

I've made a toolchain for mips64el - binutils 2.17.90 + gcc 3.3.6 + glibc 2.3.6.
I've successfully compile a linux 2.16.62 kernel and run it in qemu.
But when I try to execute dynamically compiled "Hello world" program - I' ve got a SIGSEGV"

do_page_fault() #2: sending SIGSEGV to a.out for invalid write access to
000000555556a7a7 (epc == 0000005555558010, ra == 0000005555557cd0)
@@@ do_page_fault
Segmentation fault

Statically linked executables are running without any problem!

If I use gcc 4.1.3 + glibc 2.7 + binutils 2.19 - everything ok.
I tried to install binutils 2.19 instead of binutils 2.17 (binutils 2.19, gcc 3.3.6 and glibc 2.3.6) - and dynamically linked programs are running.

So, I think it is a compiler problem, isn'it?
Does anybody have such problem? Or mips64 platform and gcc 3.3.6 are not compatible?

Thanks!


             reply	other threads:[~2009-08-19  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19 11:53 Sergey Anosov [this message]
2009-08-19 11:55 ` Paolo Carlini
2009-08-19 12:13 ` complete_unrolli / complete_unroll Albert Cohen
2009-08-19 12:33   ` Richard Guenther
2009-08-19 12:35     ` Richard Guenther
2009-08-19 13:56     ` Albert Cohen
2009-08-19 14:44       ` Albert Cohen
2009-08-19 15:09         ` Richard Guenther
2009-08-19 20:30           ` Richard Guenther
2009-08-20  8:45             ` Albert Cohen
2009-08-20  9:57               ` Richard Guenther
2009-08-20 13:34                 ` Albert Cohen
2009-09-29 18:54                 ` David Edelsohn
2009-09-30 12:36                   ` Richard Guenther

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=E1MdhYW-0005WQ-00.aserg2004-list-ru@f143.mail.ru \
    --to=aserg2004@list.ru \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).