info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
GCC > 4.4 for B2G
24 views
Skip to first unread message
Kyle Huey
Mar 14, 2014, 5:39:38 PM3/14/14
to dev-b2g
Hey everyone,
What is involved in moving B2G to a newer version of GCC?
- Kyle
What is involved in moving B2G to a newer version of GCC?
- Kyle
Dave Hylands
Mar 14, 2014, 6:18:45 PM3/14/14
to Kyle Huey, dev-b2g
My understanding is that the version of gcc we're using is based on the version of Android that b2g is being built against.
We're currently using ICS which uses gcc 4.4.
Dave Hylands
> _______________________________________________
> dev-b2g mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g
>
We're currently using ICS which uses gcc 4.4.
Dave Hylands
> dev-b2g mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g
>
Andreas Gal
Mar 14, 2014, 7:04:14 PM3/14/14
to Kyle Huey, dev-b2g
We should update our toolchain. The NDK rev 9d (March 2014) uses GCC 4.6 by default but you can also select Clang 3.4 instead. I bet Clang would speed up our builds. Coordinate with mwu. He is usually doing the work for this, but if you are impatient and want to do this right after the branch date I am sure he won’t mind.
Andreas
Kyle Huey
Mar 14, 2014, 7:06:46 PM3/14/14
to Andreas Gal, dev-b2g
- Kyle
Chris Peterson
Mar 14, 2014, 10:01:13 PM3/14/14
to mozilla...@lists.mozilla.org
Android NDK r9 also includes gcc 4.8, which might be an easier upgrade
path than switching to clang to get better code optimizations (but not
faster builds).
For reference, Firefox for Android uses NDK r8e's non-default gcc 4.7.
chris
path than switching to clang to get better code optimizations (but not
faster builds).
For reference, Firefox for Android uses NDK r8e's non-default gcc 4.7.
chris
Ehsan Akhgari
Mar 16, 2014, 7:52:45 PM3/16/14
to Andreas Gal, Kyle Huey, dev-b2g
The last time I asked about this, people told me that our partners won't
necessarily update the toolchain they use for the ICS builds so we would
have to stick with whatever toolchain they're using. Has that changed?
Cheers,
Ehsan
necessarily update the toolchain they use for the ICS builds so we would
have to stick with whatever toolchain they're using. Has that changed?
Cheers,
Ehsan
Andreas Gal
Mar 16, 2014, 7:56:12 PM3/16/14
to Ehsan Akhgari, Andreas Gal, Kyle Huey, dev-b2g
I will put you in touch with someone who can speak at least for one of them. I would assume any change we make would not be picked up before 1.5.
Andreas
Benoit Girard
Mar 17, 2014, 7:40:23 PM3/17/14
to Andreas Gal, Kyle Huey, dev-b2g
On Fri, Mar 14, 2014 at 4:04 PM, Andreas Gal <g...@mozilla.com> wrote:
>
> I bet Clang would speed up our builds.
>
I believe build unification will improve our build times much more then
>
> I bet Clang would speed up our builds.
>
clang, see bug 950676. However gsplit-dwarf should help with incremental
link times. I can't find what GCC version we need for that.
Ting-Yu Chou
Mar 17, 2014, 10:36:58 PM3/17/14
to Benoit Girard, Andreas Gal, Kyle Huey, dev-b2g
Are you looking for this?
http://gcc.gnu.org/wiki/DebugFission
<quote>
Fission is implemented in GCC 4.7, and requires support from recent versions
of objcopy and the gold linker.
Use the -gsplit-dwarf option to enable the generation of split DWARF at
compile time. This option must be used in conjunction with -c; Fission cannot
be used when compiling and linking in the same step.
</quote>
http://gcc.gnu.org/wiki/DebugFission
<quote>
Fission is implemented in GCC 4.7, and requires support from recent versions
of objcopy and the gold linker.
Use the -gsplit-dwarf option to enable the generation of split DWARF at
compile time. This option must be used in conjunction with -c; Fission cannot
be used when compiling and linking in the same step.
</quote>
0 new messages