Hello.
Is there any way to make std::locale work on illumos?
I see the following bug report
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15992 and it is
still actual for gcc 4.8.3. (Don't know why it's marked "INVALID").
--
System Administrator of Southern Federal University Computer Center
I am looking to implement one of the c++14 features " Member
initializers and aggregates(N3653). I am just wondering if anybody is
working on it right now?( I dont want to step on anybody's toes) I
see already Clang implemented it already.
Snapshot gcc-4.8-20140814 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20140814/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Dear gcc contributors,
I am very happy to announce that “Integration of ISL code generator
into Graphite” project moves to the phase of testing! I would be
very grateful for your comments and feedback about its new isl support,
which can be activated by the flag: “ -fgraphite-code-generator=isl"
> From: Joern Rennecke [mailto:joern.renne...@embecosm.com]
> Sent: Thursday, August 14, 2014 4:52 PM
>
> Newlib also has an integer-only printf implementation, but in this case,
> the default is the other way round - you have to use functions with
> nonstandard
> names to use the integer-only imp
> On Aug 14, 2014, at 1:45 AM, Kyrill Tkachov wrote:
>
>
>> On 13/08/14 18:32, Segher Boessenkool wrote:
>>> On Wed, Aug 13, 2014 at 03:57:31PM +0100, Richard Earnshaw wrote:
>>> The problem with the frankenmonster patterns is that they tend to
>>> proliferate into the machine description, and
For embedded targets with small memories and static linking, the size of
functions like *printf and their dependencies is painful, particularily for
targets that need software floating point.
avr-libc has long had a printf / scanf implementation that by default does not
include floating point supp
On 13/08/14 18:32, Segher Boessenkool wrote:
On Wed, Aug 13, 2014 at 03:57:31PM +0100, Richard Earnshaw wrote:
The problem with the frankenmonster patterns is that they tend to
proliferate into the machine description, and before you know where you
are the back-end is full of them.
Furthermore
