Re: Apple, iPhone, and GPLv3 troubles

2008-09-23 Thread Peter O'Gorman
Yuhong Bao wrote: > and Apple uses GCC (which is now under GPLv3) and Mac OS X on it. > Unfortunately, the iPhone is incompatible with GPLv3, if you want more see > the link I mentioned. Apple does not use a GPLv3 version of GCC. All GPL sources used in the iPhone, are, as far as I know, available

Re: Apple, iPhone, and GPLv3 troubles

2008-09-23 Thread Paolo Bonzini
> Off-topic, but I feel this is important, since Apple contributed to gcc, > and it is licensed under GPLv3 now. The license of GCC does not matter, unless the iPhone includes a copy of GCC's binaries for a recent-enough version. In which case, of course, Apple would be violating the GPLv3 and yo

Re: Apple, iPhone, and GPLv3 troubles

2008-09-23 Thread Yuhong Bao
1) This is offtopic. Yeah, but I want to bring this up because I can tell it is affecting GCC development. From http://gcc.gnu.org/ml/gcc/2008-02/msg00523.html: "> If someone steps forward, are you allowed to follow the patches list We can't read the patches nor gcc list. and give feedback an

Re: Apple, iPhone, and GPLv3 troubles

2008-09-23 Thread Ian Lance Taylor
"Yuhong Bao" <[EMAIL PROTECTED]> writes: > Off-topic, but I feel this is important, since Apple contributed to gcc, and > it is licensed under GPLv3 now. > In particular, this was inspired by this thread on the gcc mailing lists: > http://gcc.gnu.org/ml/gcc/2008-02/msg00520.html > Notice that I CC

Apple, iPhone, and GPLv3 troubles

2008-09-23 Thread Yuhong Bao
Off-topic, but I feel this is important, since Apple contributed to gcc, and it is licensed under GPLv3 now. In particular, this was inspired by this thread on the gcc mailing lists: http://gcc.gnu.org/ml/gcc/2008-02/msg00520.html Notice that I CCed an Apple-internal email address extracted from t

Re: C/C++ FEs: Do we really need three char_type_nodes?

2008-09-23 Thread Joe Buck
On Tue, Sep 23, 2008 at 05:51:23PM -0400, Jason Merrill wrote: > Mark Mitchell wrote: > >Is that desirable? Type-based alias analysis should be able to take > >advantage of the difference between them; a "char **" and a "signed char > >**" cannot point at the same thing, for example. > > They can

Re: C/C++ FEs: Do we really need three char_type_nodes?

2008-09-23 Thread Jason Merrill
Mark Mitchell wrote: Is that desirable? Type-based alias analysis should be able to take advantage of the difference between them; a "char **" and a "signed char **" cannot point at the same thing, for example. They can. In C++, a char* (or unsigned char*) can alias anything, and any signed/

Q: how to sometimes forcebly invoke cc1 thru gcc even without any input files?

2008-09-23 Thread Basile STARYNKEVITCH
Hello All On the MELT branch, I need sometimes that cc1 be run even if there is no input files. This is an unusual mode, but sometimes needed (This actually is needed to have MELT lisp files translated into C; for reasons not explained here, this is a special mode of my ./cc1 which does that;

Re: m32c: pointer math vs sizetype again

2008-09-23 Thread DJ Delorie
> NEGATE_EXPR on an unsigned type is fully defined. It's what you > should get when you say "unsigned int i, j; ...; i = - j;". I didn't say it was undefined, I said it seemed wrong. Esp since the example starts with a plain "int" value. > I think the problem you are facing may be that POINTER