All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: Merging Linaro gcc-4.7 hardfp support
Date: Wed, 01 May 2013 00:07:25 -0400	[thread overview]
Message-ID: <20130501040725.GA5688@denix.org> (raw)
In-Reply-To: <20130422210740.GB28316@denix.org>

On Mon, Apr 22, 2013 at 05:07:40PM -0400, Denys Dmytriyenko wrote:
> All,
> 
> As I have received mostly positive feedback from our teams (LCPD, AMSDK, 
> MCSDK) about early testing of the Linaro gcc-4.7 hardfp toolchain integartion, 
> I will be merging it into the master branch shortly. Please let me know if you 
> have any questions or concerns. Thanks.

All,

There's been slight delay in merging the Linaro-hardfp integration into the 
master branch due to few concerns raised by the kernel team last week. All 
has been resolved so far and I'll do the merge shortly, but since this may 
affect others, here are the details:


1. Compiling the same kernel tree with old gcc-4.5 and the new gcc-4.7 shows 
_less_ warnings. Some of the "variable may be used uninitialized" warnings are 
no longer reported, since gcc-4.7 is now able to remove more false positives:
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings


2. Building ARM kernel results in the following unusual warnings:

arch/arm/boot/compressed/head.S: Assembler messages:
arch/arm/boot/compressed/head.S:565: Warning: (null)
arch/arm/boot/compressed/head.S:676: Warning: (null)
arch/arm/boot/compressed/head.S:698: Warning: (null)

That is due to the changes made in recent binutils, related to ARMv8, and 
there is a patch with more details available (still pending for 3.10):
https://patchwork.kernel.org/patch/2013211/


3. Again, comparing to the previous builds under old toolchain, there are some 
"section mismatch" warnings missing, when built with the new toolchain, e.g.:

WARNING: vmlinux.o(.text+0x22ea4): Section mismatch in reference from the
function omapdrm_init() to the function .init.text:omap_device_build()
The function omapdrm_init() references
the function __init omap_device_build().
This is often because omapdrm_init lacks a __init
annotation or the annotation of omap_device_build is wrong.

After some investigation, a kernel patch was submitted by Tom Rini:
https://patchwork.kernel.org/patch/2486601/


Now, with all of the above concerns resolved I'll proceed with merging the 
linaro-hardfp branch into the master. Please let me know if you have any 
questions. Thanks.

-- 
Denys


      reply	other threads:[~2013-05-01  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 21:07 Merging Linaro gcc-4.7 hardfp support Denys Dmytriyenko
2013-05-01  4:07 ` Denys Dmytriyenko [this message]

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=20130501040725.GA5688@denix.org \
    --to=denys@ti.com \
    --cc=meta-arago@arago-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.