Re: Issues building gcc natively on mipsel

2018-07-31 Thread Jonathan Wakely
On Tue, 31 Jul 2018 at 07:25, martin krastev wrote: > > Hello, > > I'm trying to build gcc-7.3.0 (md5 747d5010b7c6938b480bc6e4d7c4be9a of > tar.gz) natively on a MACHTYPE=mipsel-unknown-linux-gnu MIPS p5600 machine > under Debian Stretch. I'm getting an illegal instruction during libstdc++ > build

Re: Issues building gcc natively on mipsel

2018-07-31 Thread YunQiang Su
Jonathan Wakely 于2018年7月31日周二 下午4:37写道: > > On Tue, 31 Jul 2018 at 07:25, martin krastev wrote: > > > > Hello, > > > > I'm trying to build gcc-7.3.0 (md5 747d5010b7c6938b480bc6e4d7c4be9a of > > tar.gz) natively on a MACHTYPE=mipsel-unknown-linux-gnu MIPS p5600 machine > > under Debian Stretch. I'

Re: ChangeLog's: do we have to?

2018-07-31 Thread Maciej W. Rozycki
On Thu, 5 Jul 2018, Tom Tromey wrote: > I use git-merge-changelog from gnulib. If you want to use git am and > avoid manually copying ChangeLog text from the commit message back into > the appropriate files, then it's much better to install the driver and > include the ChangeLog diffs in the patc

Re: ChangeLog's: do we have to?

2018-07-31 Thread Trevor Saunders
On Wed, Aug 01, 2018 at 12:16:57AM +0100, Maciej W. Rozycki wrote: > On Thu, 5 Jul 2018, Tom Tromey wrote: > > > I use git-merge-changelog from gnulib. If you want to use git am and > > avoid manually copying ChangeLog text from the commit message back into > > the appropriate files, then it's mu

Re: ChangeLog's: do we have to?

2018-07-31 Thread Trevor Saunders
ga, forgot to attach the script in my previous message, so here it is. thanks Trev On Wed, Aug 01, 2018 at 12:16:57AM +0100, Maciej W. Rozycki wrote: > On Thu, 5 Jul 2018, Tom Tromey wrote: > > > I use git-merge-changelog from gnulib. If you want to use git am and > > avoid manually copying Ch

A question about acquire/release semantic in the wiki page

2018-07-31 Thread Bramandia Ramadhana
Hi, I am reading the gcc wiki page about atomic Acquire/Release memory model: https://gcc.gnu.org/wiki/Atomic/GCCMM/AtomicSync. It is mentioned: "Both of these asserts can pass since there is no ordering imposed between the stores in thread 1 and thread 2. If this example were written using the