On 10/5/2022 7:26 pm, Sebastian Huber wrote:
> On 10/05/2022 10:28, Chris Johns wrote:
>> On 10/5/2022 1:13 am, Sebastian Huber wrote:
>>> Hello Karel,
>>>
>>> On 09/05/2022 17:09, Karel Gardas wrote:
I'm just curious is there any reason to use GCC from git (post release
version) and not
On 10/05/2022 10:28, Chris Johns wrote:
On 10/5/2022 1:13 am, Sebastian Huber wrote:
Hello Karel,
On 09/05/2022 17:09, Karel Gardas wrote:
I'm just curious is there any reason to use GCC from git (post release
version) and not vanilla 12.1 release tarball from gcc.gnu.org?
this makes it easie
On 10/5/2022 1:13 am, Sebastian Huber wrote:
> Hello Karel,
>
> On 09/05/2022 17:09, Karel Gardas wrote:
>> I'm just curious is there any reason to use GCC from git (post release
>> version) and not vanilla 12.1 release tarball from gcc.gnu.org?
>
> this makes it easier to pick up a GCC 12 releas
Hello Karel,
On 09/05/2022 17:09, Karel Gardas wrote:
I'm just curious is there any reason to use GCC from git (post release
version) and not vanilla 12.1 release tarball from gcc.gnu.org?
this makes it easier to pick up a GCC 12 release branch which includes
fixes relevant to RTEMS users.
Hello Sebastian,
thanks a lot for dealing with GCC 12 update. I'm just curious is there
any reason to use GCC from git (post release version) and not vanilla
12.1 release tarball from gcc.gnu.org?
Thanks!
Karel
On 5/9/22 14:54, Sebastian Huber wrote:
Hello,
I updated the RSB to use the l
Hello,
I updated the RSB to use the latest GCC 12 release branch version. GCC
12.1 was released on May 6th:
https://gcc.gnu.org/gcc-12/changes.html
One interesting GCC 12 feature for embedded systems is the default
initialization of stack variables:
https://gcc.gnu.org/onlinedocs/gcc-12.1.
