Re: basic VRP min/max range overflow question

2005-06-18 Thread Tristan Wibberley
my_array[sizeof(my_array) / sizeof(*my_array)] = 0; I believe this is theoretically impossible in general. -- Tristan Wibberley Opinions expressed are my own and certainly *not* those of my employer, etc.

Re: 4.2 Project: "@file" support

2005-08-25 Thread Tristan Wibberley
; being used for switches is bad enough without another valid filename character being overloaded. At least the '-' problem is well understood and people can avoid using filenames beginning with '-'. -- Tristan Wibberley Opinions expressed are my own and do not necessarily coincide with those of my employer, etc.

Re: 4.2 Project: "@file" support

2005-08-26 Thread Tristan Wibberley
Mark Mitchell wrote: > Tristan Wibberley wrote: > >> Mark Mitchell wrote: >> >> >> >>> However, there's demonstrable interest in this feature for GNU/Linux as >>> well, from the lists, and for Java on all operating systems. >>> >&

Re: funny problem with g++

2005-12-07 Thread Tristan Wibberley
o define a zero length array *does* make sense. The alternative is to hide the array in an extra layer of templates, and to specialise it for zero to not use a real array in its implementation, and that's so nasty. IMHO, this is a good extension, at least until boost::array gets standardised. -- Tristan Wibberley

Re: why are we not using const?

2006-06-27 Thread Tristan Wibberley
e_node const *const_tree; void f(const_tree a); *would* be meaningful, however. -- Tristan Wibberley

Re: gcc visibility used by moz

2006-07-11 Thread Tristan Wibberley
instances via exported functions, access any visible or virtual members, and pass the pointers back into visible functions of the shared object - or even dereference the pointers to pass by reference. -- Tristan Wibberley These opinions are my own, and do not reflect those of my employer.

Re: gcc visibility used by moz

2006-07-12 Thread Tristan Wibberley
Daniel Jacobowitz wrote: On Wed, Jul 12, 2006 at 02:04:37AM +0100, Tristan Wibberley wrote: If the programmer had intended that the type should appear to not exist. it wouldn't be defined in a header #include-able by client code. The GCC doesn't know if the header is includable

Re: gcc visibility used by moz

2006-07-12 Thread Tristan Wibberley
Daniel Jacobowitz wrote: On Wed, Jul 12, 2006 at 02:04:37AM +0100, Tristan Wibberley wrote: If the programmer had intended that the type should appear to not exist. it wouldn't be defined in a header #include-able by client code. The GCC doesn't know if the header is includable

Re: gcc visibility used by moz

2006-07-12 Thread Tristan Wibberley
Mike Stump wrote: On Jul 12, 2006, at 11:49 AM, Tristan Wibberley wrote: "the client code needs to know about the existence of this type so it can get pointers and references to instances and pass them back in later and maybe be able to call virtual member functions and access non-s

Re: gcc visibility used by moz

2006-07-12 Thread Tristan Wibberley
Gabriel Dos Reis wrote: Tristan Wibberley <[EMAIL PROTECTED]> writes: | The programmer says: | | "the client code needs to know about the existence of this type so it | can get pointers and references to instances and pass them back in | later and maybe be able to call vir

Re: gcc visibility used by moz

2006-07-12 Thread Tristan Wibberley
Daniel Jacobowitz wrote: On Wed, Jul 12, 2006 at 07:49:21PM +0100, Tristan Wibberley wrote: No, that's why we need programmer provided attributes. The programmer says: "the client code needs to know about the existence of this type so it can get pointers and references to instance

Re: gcc visibility used by moz

2006-07-12 Thread Tristan Wibberley
ning since they may be trying to do some clever multi-language interoperability thing. -- Tristan Wibberley These opinions are my own, and do not reflect those of my employer.

Re: gcc visibility used by moz

2006-07-12 Thread Tristan Wibberley
Gabriel Dos Reis wrote: Tristan Wibberley <[EMAIL PROTECTED]> writes: [...] | I am suggesting that visibility attributes should *not* touch the C++ | type system in any way. But then, at the same time you're talking of polymorphic types (e.g. vtables). vtables happen to jus

poor optimisation case

2007-08-05 Thread Tristan Wibberley
to special case the first element of a sequence and when used in a generic algorithm which just has the simple loop of -DNEW it ought to be optimised like -DOLD if inlining occurs. -- Tristan Wibberley Any opinion expressed is mine (or else I'm playing devils advocate for the sake of a

Re: poor optimisation case

2007-08-05 Thread Tristan Wibberley
amming problem that I need help with (I know how to micro-optimise with C-style ugly-stuff). I'm just reporting a significant missed optimisation opportunity that will help C++ developers even if not C or fortran developers. The only reason I didn't reflect the C++ simple-vs-spaghetti code issue in m

Re: poor optimisation case

2007-08-06 Thread Tristan Wibberley
On Mon, 2007-08-06 at 07:38 -0700, Ian Lance Taylor wrote: > Tristan Wibberley <[EMAIL PROTECTED]> writes: > > > I've found a case which looks like it should be possible to optimise but > > gcc (very recent trunk) isn't doing which could give improvements in &g