I have no plan for willful obstruction in solving this recurring and
really annoying
problem that trips up users again and again, under all kinds of
reasons (both perceived
or constructed.)
Snapshot gcc-4.7-20120616 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20120616/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Hi,
On Fri, 15 Jun 2012, Gabriel Dos Reis wrote:
> On Fri, Jun 15, 2012 at 3:12 PM, James Y Knight wrote:
>
> > IMO, at the /very least/, libstdc++ should go ahead and change std::string
> > to be the new implementation. Once std::string is ABI-incompatible between
> > the modes, there's basica
Arch hvv writes:
> Have anybody inspected it? Is GPL violated in this case or not (e.g.
> do they provide all patches they've made to gcc)?
If they provide the source code to anybody who purchases their package,
then they are doing nothing wrong according to the GPL. I don't know
whether they d
Hi,
On Sat, 16 Jun 2012, Jonathan Wakely wrote:
> On 16 June 2012 12:01, Arch hvv wrote:
> > Have anybody inspected it? Is GPL violated in this case or not (e.g.
> > do they provide all patches they've made to gcc)?
>
> If it's based on llvm-gcc then it only uses GCC as the front-end so
> there
On 16 June 2012 12:01, Arch hvv wrote:
> Have anybody inspected it? Is GPL violated in this case or not (e.g.
> do they provide all patches they've made to gcc)?
If it's based on llvm-gcc then it only uses GCC as the front-end so
there may be no reason to patch GCC.
Hello,
Just found morpher dot com - it's based on GCC:
Morpher is a compiler driven obfuscation solution for
C/C++/ObjC/ObjC++. Being a compiler, our tool has much more structural
information than any other tool that works directly with binary
format. Therefore the abilities of Morpher's C++ sour
On 15/06/12 21:45, Gabriel Dos Reis wrote:
On Fri, Jun 15, 2012 at 3:12 PM, James Y Knight wrote:
IMO, at the /very least/, libstdc++ should go ahead and change std::string
to be the new implementation. Once std::string is ABI-incompatible between
the modes, there's basically no chance that an
