X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
Date: Thu, 28 Nov 2013 12:05:20 -0500
Message-Id: <201311281705.rASH5KiD027835@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <82676ab0-7e81-4b89-bc7a-e3360d6c3b93@googlegroups.com> (message
	from John Davidson on Thu, 28 Nov 2013 01:34:05 -0800 (PST))
Subject: Re: Using DJGPP for C++ DOS development today?
References: <0404a92b-e194-4e75-97b5-58c8e5b3c076 AT googlegroups DOT com>
 <52957941 DOT 9050203 AT iki DOT fi> <57ae09cc-bc48-4dcf-978d-9078096b2127 AT googlegroups DOT com>
 <bfnhrrF6qghU1 AT mid DOT dfncis DOT de> <82676ab0-7e81-4b89-bc7a-e3360d6c3b93 AT googlegroups DOT com>
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> I found this:
> https://groups.google.com/forum/#!topic/comp.os.msdos.djgpp/WeMjxnR1NBc
> which seems to indicate that GCC will output non-386 opcodes anyway :-(

Only for atomic operations, which are typically only used when
threading, and DJGPP doesn't support threading.

> http://gcc.gnu.org/onlinedocs/libstdc++/faq.html says:
> "Only when actually running the code on a i386 will the problem appear.
> This is fixed in 3.2.2."

DJGPP's copy of gcc is up to version 4.8, so we're well past that fix.