Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-13 Thread Ollie Wild
On 9/13/07, Mark Mitchell <[EMAIL PROTECTED]> wrote: > I wouldn't characterize my objections as terribly strong. It's > certainly nothing against distcc or ccache. But, I think these kinds of > mentions are odd to put in our documentation. The manual should say > what the options do. Referenci

Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-13 Thread Mark Mitchell
Ollie Wild wrote: > On 9/13/07, Tom Tromey <[EMAIL PROTECTED]> wrote: >>> "Ollie" == Ollie Wild <[EMAIL PROTECTED]> writes: >> Ollie> One quick question. When I updated the gcc info page, Mark >> Ollie> Mitchell felt strongly that it shouldn't mention distcc or >> Ollie> ccache directly. Howe

Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-13 Thread Ollie Wild
On 9/13/07, Tom Tromey <[EMAIL PROTECTED]> wrote: > > "Ollie" == Ollie Wild <[EMAIL PROTECTED]> writes: > > Ollie> One quick question. When I updated the gcc info page, Mark > Ollie> Mitchell felt strongly that it shouldn't mention distcc or > Ollie> ccache directly. However, I think it's a g

Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-13 Thread Tom Tromey
> "Ollie" == Ollie Wild <[EMAIL PROTECTED]> writes: Ollie> One quick question. When I updated the gcc info page, Mark Ollie> Mitchell felt strongly that it shouldn't mention distcc or Ollie> ccache directly. However, I think it's a good idea to give Ollie> users some idea what the option is

Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-11 Thread Ollie Wild
On 9/11/07, Gerald Pfeifer <[EMAIL PROTECTED]> wrote: > On Tue, 11 Sep 2007, Tom Tromey wrote: > >> Also, I recently added a new -fdirectives-only option which improves > >> distcc and ccache performance. Does that merit a release note update > > as well? > > IMO, yes. > > Seconded. :-) OK. I'll

Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-11 Thread Gerald Pfeifer
On Tue, 11 Sep 2007, Tom Tromey wrote: >> Also, I recently added a new -fdirectives-only option which improves >> distcc and ccache performance. Does that merit a release note update > as well? > IMO, yes. Seconded. :-) Gerald

Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-11 Thread Tom Tromey
> "Ollie" == Ollie Wild <[EMAIL PROTECTED]> writes: Ollie> Also, I recently added a new -fdirectives-only option which improves Ollie> distcc and ccache performance. Does that merit a release note update Ollie> as well? IMO, yes. Tom

Re: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-11 Thread Ollie Wild
On 9/9/07, Gerald Pfeifer <[EMAIL PROTECTED]> wrote: > Ollie, would you mind adding a snippet to htdocs/gcc-4.3/changes.html > in the wwwdocs module of our CVS repository? If you need any help with > that, please let me know. Sent to gcc-patches at http://gcc.gnu.org/ml/gcc-patches/2007-09/msg010

RE: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-09 Thread Gerald Pfeifer
On Tue, 4 Sep 2007, Dave Korn wrote: > On 04 September 2007 10:05, me wrote: >> The point of this is that __COUNTER__ would assign consecutive numbers > >> I can not find g++'s equivalent & wonder how I could achieve the same >> thing? > This feature was just added recently. It will be in all upco

RE: Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-04 Thread Dave Korn
On 04 September 2007 10:05, me wrote: > The point of this is that __COUNTER__ would assign consecutive numbers > I can not find g++'s equivalent & wonder how I could achieve the same > thing? This feature was just added recently. It will be in all upcoming gcc-4.3 and later series releases.

Does g++ have a intel/msdn __COUNTER__ macro equivalent??

2007-09-04 Thread me
Dear Sir/Madam I'm trying to specify random distributions throughout my program eg Uniform(1,0), Normal(10,2). Id like these replaced at the pre-processing stage with Uniform(__COUNTER__,1,0) & Normal(__COUNTER__,10,2) using macros such as #define U(a,b) U(__COUNTER__,a,b) etc The point of this