public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tgard at opentext dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/60984] [4.9 Regression] AIX: gcc-4.9.0 bootstrap fails in stage-2
Date: Thu, 22 May 2014 12:11:00 -0000	[thread overview]
Message-ID: <bug-60984-4-DbVzhNejee@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60984-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60984

--- Comment #31 from Torbjörn Gard <tgard at opentext dot com> ---
This worked for me.
Thanks a lot :-)
>From gcc-bugs-return-452326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 22 12:13:56 2014
Return-Path: <gcc-bugs-return-452326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19313 invoked by alias); 22 May 2014 12:13:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19293 invoked by uid 48); 22 May 2014 12:13:52 -0000
From: "Nassar.Mahmood at nortechonline dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/61285] New: GCC version 4.7.x 4.8.x 4.9.x does not compile working ARM code for the AT24 EEPROM driver under Linux 3.6.x
Date: Thu, 22 May 2014 12:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: Nassar.Mahmood at nortechonline dot co.uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-61285-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-05/txt/msg02018.txt.bz2
Content-length: 1531

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida285

            Bug ID: 61285
           Summary: GCC version 4.7.x 4.8.x 4.9.x does not compile working
                    ARM code for the AT24 EEPROM driver under Linux 3.6.x
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Nassar.Mahmood at nortechonline dot co.uk

I'm working on deploying Linux on an embedded system, kernel v3.6.9.
The board is based on Atmels AT91SAM9G20, we are using BuildRoot to manage the
deployement.
The description of the system is:
Target Architecture - ARM (little endian)
Target Architecture Variant - arm926t
Target ABI - EABI
Floating point strategy - Soft float
ARM instruction set - ARM

As part of the project we plan on using a library which has been written with
C++11 code, for this we require gcc 4.8.x or 4.9.x to build the target system.
The board contains an EEPROM chip on which a unique serial number is stored,
this uses the Linux AT24 driver to access it.
My problem is that building with a gcc 4.7 toolchain onwards causes the AT24
driver to lock up the system, and eventually reboot.

I have tested this by building against gcc versions downloaded from here, the
red hat mirror, custom gcc toolchains supplied by Mentor (Sourcery).
I can replicate the issue with either C library -- uclibc or glibc.

The AT24 driver has not undergone any major changes.


  parent reply	other threads:[~2014-05-22 12:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28  9:05 [Bug bootstrap/60984] New: " tgard at opentext dot com
2014-04-28 13:46 ` [Bug bootstrap/60984] " dje at gcc dot gnu.org
2014-04-28 19:23 ` dje at gcc dot gnu.org
2014-04-28 19:41 ` dje at gcc dot gnu.org
2014-04-28 22:09 ` dje at gcc dot gnu.org
2014-04-29  7:49 ` jakub at gcc dot gnu.org
2014-04-29  7:55 ` [Bug bootstrap/60984] [4.9 Regression] " rguenth at gcc dot gnu.org
2014-04-29 12:54 ` dje at gcc dot gnu.org
2014-04-29 14:11 ` tgard at opentext dot com
2014-04-29 17:01 ` dje at gcc dot gnu.org
2014-04-29 17:56 ` dje at gcc dot gnu.org
2014-05-02  7:59 ` tgard at opentext dot com
2014-05-02 13:29 ` tgard at opentext dot com
2014-05-04 20:13 ` dje at gcc dot gnu.org
2014-05-05  7:18 ` tgard at opentext dot com
2014-05-05 15:25 ` tgard at opentext dot com
2014-05-08  1:18 ` dje at gcc dot gnu.org
2014-05-08  2:05 ` dje at gcc dot gnu.org
2014-05-08  3:00 ` dje at gcc dot gnu.org
2014-05-08 17:42 ` dje at gcc dot gnu.org
2014-05-09 14:29 ` hubicka at gcc dot gnu.org
2014-05-09 15:44 ` dje at gcc dot gnu.org
2014-05-09 15:53 ` dje at gcc dot gnu.org
2014-05-10 14:57 ` dje at gcc dot gnu.org
2014-05-10 15:34 ` dje at gcc dot gnu.org
2014-05-20 22:48 ` hubicka at ucw dot cz
2014-05-20 23:02 ` dje at gcc dot gnu.org
2014-05-20 23:23 ` hubicka at ucw dot cz
2014-05-21  1:45 ` dje at gcc dot gnu.org
2014-05-21  5:40 ` hubicka at gcc dot gnu.org
2014-05-21  5:42 ` hubicka at gcc dot gnu.org
2014-05-21  5:45 ` hubicka at gcc dot gnu.org
2014-05-22 12:11 ` tgard at opentext dot com [this message]
2014-05-22 21:06 ` fbissey at slingshot dot co.nz

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=bug-60984-4-DbVzhNejee@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).