All of lore.kernel.org
 help / color / mirror / Atom feed
* Known toolchain bug?
@ 2014-02-14 14:27 Wolfgang Denk
  2014-02-14 14:43 ` Gary Thomas
  0 siblings, 1 reply; 4+ messages in thread
From: Wolfgang Denk @ 2014-02-14 14:27 UTC (permalink / raw)
  To: yocto

Hello,

in message [1] on the Linaro mailing list, Koen Kooi reported a
toolchain problem.  I can reproduce the same problem both in Yocto
1.5.1 and witht he current top-of-tree; for example, using the latest
autobuilder result
core-image-sato-sdk-imx53qsb-20140213124023.rootfs.tar.bz2
I get this [source of Koen's test program attached]:

root@imx53qsb:/tmp# g++ -Wall -std=c++11 -o b -lpthread b.cpp 
root@imx53qsb:/tmp# ./b
pure virtual method called
terminate called without an active exception
Aborted

Is this a (known?) tool chain issue, or am I missing something?


[1] http://article.gmane.org/gmane.linux.linaro.toolchain/3925


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"And they told us, what they wanted... Was a sound  that  could  kill
some-one, from a distance."                               - Kate Bush


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Known toolchain bug?
  2014-02-14 14:27 Known toolchain bug? Wolfgang Denk
@ 2014-02-14 14:43 ` Gary Thomas
  2014-02-15  1:46   ` Khem Raj
  0 siblings, 1 reply; 4+ messages in thread
From: Gary Thomas @ 2014-02-14 14:43 UTC (permalink / raw)
  To: yocto

On 2014-02-14 07:27, Wolfgang Denk wrote:
> Hello,
> 
> in message [1] on the Linaro mailing list, Koen Kooi reported a
> toolchain problem.  I can reproduce the same problem both in Yocto
> 1.5.1 and witht he current top-of-tree; for example, using the latest
> autobuilder result
> core-image-sato-sdk-imx53qsb-20140213124023.rootfs.tar.bz2
> I get this [source of Koen's test program attached]:

Source code attachment missing?

> 
> root@imx53qsb:/tmp# g++ -Wall -std=c++11 -o b -lpthread b.cpp 
> root@imx53qsb:/tmp# ./b
> pure virtual method called
> terminate called without an active exception
> Aborted
> 
> Is this a (known?) tool chain issue, or am I missing something?
> 
> 
> [1] http://article.gmane.org/gmane.linux.linaro.toolchain/3925
> 
> 
> Best regards,
> 
> Wolfgang Denk
> 

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Known toolchain bug?
  2014-02-14 14:43 ` Gary Thomas
@ 2014-02-15  1:46   ` Khem Raj
  0 siblings, 0 replies; 4+ messages in thread
From: Khem Raj @ 2014-02-15  1:46 UTC (permalink / raw)
  To: Gary Thomas; +Cc: Yocto list discussion

Hello Wolfgang

On Feb 14, 2014, at 6:43 AM, Gary Thomas <gary@mlbassoc.com> wrote:

> On 2014-02-14 07:27, Wolfgang Denk wrote:
>> Hello,
>> 
>> in message [1] on the Linaro mailing list, Koen Kooi reported a
>> toolchain problem.  I can reproduce the same problem both in Yocto
>> 1.5.1 and witht he current top-of-tree; for example, using the latest
>> autobuilder result
>> core-image-sato-sdk-imx53qsb-20140213124023.rootfs.tar.bz2
>> I get this [source of Koen's test program attached]:
> 
> Source code attachment missing?
> 
>> 
>> root@imx53qsb:/tmp# g++ -Wall -std=c++11 -o b -lpthread b.cpp 
>> root@imx53qsb:/tmp# ./b
>> pure virtual method called
>> terminate called without an active exception
>> Aborted
>> 
>> Is this a (known?) tool chain issue, or am I missing something?
>> 

as you can see this was a problem reported by your truly :)

infact, its an issue seen for gcc4.8 and arm architecture thus far seems to work fine for x86. It also works ok with gcc 4.7 on arm but given that c++11 is new there is something to fix there for arm. I hope linaro toolchain group has taken a note of this issue. as you can see its not only seen in Linaro toolchain which was my initial thought. but its also prevalent in upstream 4.8 gcc. I haven’t tested gcc 4.9 may be its fixed there.


>> 
>> [1] http://article.gmane.org/gmane.linux.linaro.toolchain/3925
>> 
>> 
>> Best regards,
>> 
>> Wolfgang Denk
>> 
> 
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Known toolchain bug?
@ 2014-02-16 12:26 Wolfgang Denk
  0 siblings, 0 replies; 4+ messages in thread
From: Wolfgang Denk @ 2014-02-16 12:26 UTC (permalink / raw)
  To: Gary Thomas; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

Dear Gary Thomas,

In message <52FE2B80.9030907@mlbassoc.com> you wrote:
> > 
> > in message [1] on the Linaro mailing list, Koen Kooi reported a
> > toolchain problem.  I can reproduce the same problem both in Yocto
> > 1.5.1 and witht he current top-of-tree; for example, using the latest
> > autobuilder result
> > core-image-sato-sdk-imx53qsb-20140213124023.rootfs.tar.bz2
> > I get this [source of Koen's test program attached]:
> 
> Source code attachment missing?

Sorry.  Here it is...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Is the glass half empty, half full, or twice as large as it needs to


[-- Attachment #2: b.cpp --]
[-- Type: text/plain , Size: 380 bytes --]

#include <iostream>
#include <thread>
#include <mutex>

std::mutex mx;
int i;

void thrfunc();

int main(void)
{
   i=0;
   std::thread          thr1(thrfunc),thr2(thrfunc);

   thr1.join();
   thr2.join();

   return 0;
}

void thrfunc()
{
   mx.lock();
   i++;
   std::cout << std::this_thread::get_id() << " i: " << i << std::endl;
   mx.unlock();
}

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-02-16 12:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-14 14:27 Known toolchain bug? Wolfgang Denk
2014-02-14 14:43 ` Gary Thomas
2014-02-15  1:46   ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2014-02-16 12:26 Wolfgang Denk

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.