<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta/recipes-devtools/gcc, branch mickledore-4.2.2</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=mickledore-4.2.2</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=mickledore-4.2.2'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2023-06-30T14:07:59+00:00</updated>
<entry>
<title>gcc : upgrade to v12.3</title>
<updated>2023-06-30T14:07:59+00:00</updated>
<author>
<name>Sundeep KOKKONDA</name>
<email>sundeep.kokkonda@windriver.com</email>
</author>
<published>2023-06-23T16:40:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=769673babcfe2a6b48911a3f898a4a0baec37b1e'/>
<id>urn:sha1:769673babcfe2a6b48911a3f898a4a0baec37b1e</id>
<content type='text'>
gcc stable version upgraded from v12.2 to v12.3

Below is the bug fix list for v12.3
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&amp;resolution=FIXED&amp;target_milestone=12.3

(From OE-Core rev: 5aacf91e9839f60f5cb933e27a349c2ed7fcddf4)

Signed-off-by: Sundeep KOKKONDA &lt;sundeep.kokkonda@windriver.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>gcc-shared-source: do not use ${S}/.. in deploy_source_date_epoch</title>
<updated>2023-03-25T09:39:28+00:00</updated>
<author>
<name>Peter Marko</name>
<email>peter.marko@siemens.com</email>
</author>
<published>2023-03-23T12:25:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b553853fc44d4380267c80396c9e4f56fe026cd8'/>
<id>urn:sha1:b553853fc44d4380267c80396c9e4f56fe026cd8</id>
<content type='text'>
This function is referencing '${S}/..'.
It uses ${S} only as good known directory path to start
traversing from, and it does not need it to exist or be populated.
If ${S} does not exist yet, the function will fail because
it cannot evaluate path .. from non-existing directory.

Reproducer (verified in master and kirkstone):
  bitbake gcc -c deploy_source_date_epoch
  bitbake gcc -c cleansstate
  rm -rf build/tmp
  bitbake gcc -c deploy_source_date_epoch

(From OE-Core rev: 42661a59cda164b2d236ffc35b4d8cf43312b677)

Signed-off-by: Peter Marko &lt;peter.marko@siemens.com&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>recipes: add support for loongarch64</title>
<updated>2023-03-23T22:36:46+00:00</updated>
<author>
<name>Jialing Zhang</name>
<email>zhangjialing@loongson.cn</email>
</author>
<published>2023-03-22T06:50:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=13c1529b70345b0446482e8952e0b4b452bce7b1'/>
<id>urn:sha1:13c1529b70345b0446482e8952e0b4b452bce7b1</id>
<content type='text'>
glibc gcc vulkan add support for loongarch64

(From OE-Core rev: 526b9a8ebacf07690dfc5beb1788ab7a5bef8423)

Signed-off-by: Jialing Zhang &lt;zhangjialing@loongson.cn&gt;
Signed-off-by: Qizheng Zhu &lt;zhuqizheng@loongson.cn&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc-source: Ensure deploy_source_date_epoch sstate hash doesn't change</title>
<updated>2022-11-07T21:57:21+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-11-07T14:14:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=2cdaa164e8b4618a82ccd3fcb87cf58e36b6d6d3'/>
<id>urn:sha1:2cdaa164e8b4618a82ccd3fcb87cf58e36b6d6d3</id>
<content type='text'>
Currently if you switch machines, gcc-source do_deploy_source_date_epoch
would re-run as the stamps are tune specific. This hasn't caused much
of an issue until now, however if we fix the gcc recipes to reuse the
timestamp from this task, it does then create problems.

Copy code from allarch to ensure this task hash doesn't change between
machines/tunes.

(From OE-Core rev: 7e052d03464ba5e880a6c5a0e45ff2f467ef97e8)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc-source: Drop gengtype manipulation</title>
<updated>2022-11-07T21:57:21+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-11-03T12:41:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=82d294860b07a0726664b1ac1e9db6517ae25fca'/>
<id>urn:sha1:82d294860b07a0726664b1ac1e9db6517ae25fca</id>
<content type='text'>
Whilst we patch gengtype.cc, we don't patch gengtype-lex.cc which would
be the file which would trigger regeneration of files.

The real bug that was likely the cause for this fix is probably SDE issues
with gcc shared workdir so this code can now be dropped.

(From OE-Core rev: 7ab82b5db2a737c2a0266280b15d343a27c0e1d5)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc-source: Fix gengtypes race</title>
<updated>2022-11-07T21:57:21+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-11-03T10:34:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b964727e3a33d2d990891719dda2863198e8f861'/>
<id>urn:sha1:b964727e3a33d2d990891719dda2863198e8f861</id>
<content type='text'>
gcc renamed .c files to .cc files:

https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=5c69acb32329d49e58c26fa41ae74229a52b9106

but we didn't fix this reference which meant we re-introduced a race around
gengtypes-lex.c. This lead to the race reappearing on the autobuilder. Fix
the naming to avoid the problem again.

[YOCTO #14953]

(From OE-Core rev: dbca40ed399405b663dbc3894e35596a2615f47d)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc-shared-source: Fix source date epoch handling</title>
<updated>2022-11-07T21:57:21+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2022-11-03T17:31:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=4b80c6cdc01e3aa2d5971b880e33f360feaa528d'/>
<id>urn:sha1:4b80c6cdc01e3aa2d5971b880e33f360feaa528d</id>
<content type='text'>
The source date epoch for gcc isn't being transferred from the shared
workdir to the current WORKDIR for the specific recipe. This results in
the clamping code within sstate.bbclass using a value from 2011 which
changes the timestamps of many files. Since this happens part way
through the build, if pieces of gcc haven't built, or build/rebuild
later, we see things rebuilding when they should not and for generated
files, races are possible.

Fix this by copying the SDE from the shared workdir into the recipe
workdir.

[YOCTO #14953]

(From OE-Core rev: b996293b4c8ab7ff3ed852045d17290df29205df)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: Allow -Wno-error=poison-system-directories to take effect</title>
<updated>2022-10-25T12:42:03+00:00</updated>
<author>
<name>Peter Kjellerstedt</name>
<email>pkj@axis.com</email>
</author>
<published>2022-10-13T13:29:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5c8103695de8861e9330d1ea9e2f42a38e1d9897'/>
<id>urn:sha1:5c8103695de8861e9330d1ea9e2f42a38e1d9897</id>
<content type='text'>
The change in commit e903b29f (gcc-cross: pass
-Werror=poison-system-directories to compiler stages) made it impossible
to disable the error using -Wno-error=poison-system-directories.

(From OE-Core rev: 1cb0245539f7d5277fae4e9abc7f2a0130d0caa8)

Signed-off-by: Peter Kjellerstedt &lt;peter.kjellerstedt@axis.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc: set the default target arch</title>
<updated>2022-09-29T20:15:50+00:00</updated>
<author>
<name>Daniel McGregor</name>
<email>daniel.mcgregor@vecima.com</email>
</author>
<published>2022-09-28T22:13:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=beea1db008dc668185c71703cd9a3ef7d0b768f4'/>
<id>urn:sha1:beea1db008dc668185c71703cd9a3ef7d0b768f4</id>
<content type='text'>
The default x86-64 architecture for target gcc (ie, the one in poky
build appliances) is native. Since we have a variety of build systems
it will occasionally produce instructions that don't work on all of
our development system.

Instead, set gcc's default architecture to the one specified in
TUNE_CC_ARCH, that guarantees that gcc-runtime and any binaries
produced are compatible with the target machine type.

(From OE-Core rev: 52b952e474e655f8b4b6501813d57e20c9f02ba2)

Signed-off-by: Daniel McGregor &lt;daniel.mcgregor@vecima.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>gcc-cross-canadian: add default plugin linker</title>
<updated>2022-09-17T06:47:07+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@gmail.com</email>
</author>
<published>2022-09-16T07:41:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=09ae62b662724c58c64b305bac05ed9302ce9d79'/>
<id>urn:sha1:09ae62b662724c58c64b305bac05ed9302ce9d79</id>
<content type='text'>
Fix multilib sdk issue where gcc is unable to find linker. Previous
fix was in cdd86896c8d29135f937968e9aa07f919cf543d3 using real-ld
symlink, but that prevented switching between bfd and gold linkers.

Running compiler with debug arguments shows that collect2 tries and
fails to find linker using the multilib triples:

  $ $CC -v -Wl,-debug
  ...
  Looking for 'real-ld'
  Looking for 'collect-ld'
  Looking for 'mips-oemllib32-linux-ld'
  Looking for 'mips-oe-linux-mips-oemllib32-linux-ld'
  ...
  collect2 version 12.2.0
  ld_file_name        = not found
  ...
  collect2: fatal error: cannot find ‘ld’

Using --with-plugin-ld=ld in gcc-cross-canadian builds to set default
linker name for collect2, lets it find the linker correctly:

  Looking for 'real-ld'
  Looking for 'collect-ld'
  Looking for 'ld'
  ...
  collect2 version 12.2.0
  ld_file_name        = /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/libexec/mips-oe-linux/gcc/mips-oe-linux/12.2.0/ld

Swith between bfd and gold linker works as expected now:

  $ $CC -v -Wl,-debug -fuse-ld=gold
  ...
  Looking for 'real-ld'
  Looking for 'collect-ld'
  Looking for 'ld.gold'
  ...
  collect2 version 12.2.0
  ld_file_name        = /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/libexec/i686-oe-linux/gcc/i686-oe-linux/12.2.0/ld.gold

(From OE-Core rev: cf1bb16b7f9f81514feaf1e4ecffd9039387bb89)

Signed-off-by: Samuli Piippo &lt;samuli.piippo@qt.io&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
