Re: gcc -Os optimisation broken (RELENG_4)

2000-03-17 Thread Sascha Schumann

On Thu, Mar 16, 2000 at 10:09:37PM -0800, Doug Barton wrote:
> Donn Miller wrote:
> > 
> > Doug Barton wrote:
> > 
> > > Hmm... If I have a PII (Actually celeron 300A) or a PIII, which is
> > > better, 'pentium' or 'pentiumpro'? I would think the latter, but I've
> > > learned not to assume where gcc is concerned.
> > 
> > I think that 'pentium' would result in code that isn't as optimized as
> > 'pentiumpro', but I've heard that 'pentium' has a lot less problems.
> > 
> > > Also, I have heard conflicting reports as to whether compiling the
> > > kernel/world with optimisations is a good thing. Anyone care to (re)open
> > > that can of worms?
> > 
> > I compile my kernel/world with -mpentium -O3 -pipe.  The only problem
> > I've seen so far were spurious random reboots that would occur about
> > 2-3 times a month.  But, that was last summer, and hasn't happened
> > since.  Something else must have been the culprit.  (Maybe -current
> > wasn't as stable last summer.)  With the aforementioned CFLAGS, I have
> > a pretty reliable and stable system.
> > 
> > I've heard that -mpentiumpro can be pretty buggy, and it can actually
> > result in slower code than -mpentium for certain pentium types.  I
> > trust plain -mpentium, as it has been very reliable for me, except for
> > some compile-time errors caused by the optimization (Qt).
> 
>   In the interests of providing another datapoint, I tried my old, boring
> P5 machine, and with -Os -march=pentium buildworld bombed trying to
> compile cc1plus in the build tools phase. Backing off to -O worked. The
> kernel was ok with -Os -march=pentium. 

In contrast, I've been using -Os -march=pentium during the last three
months for buildworld and the kernel. Never had problems whatsoever.

- Sascha


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Thoughts...

2000-01-16 Thread Sascha Schumann

On Sat, Jan 15, 2000 at 09:26:08PM -0800, Matthew Dillon wrote:
> 
> :> 
> :> There are lots of ways of syncing up that do not require sending the 
> :> entire image over the network every time.  Syncing is something you could
> :> do with an NFS mount quite easily, combined with something like cpdup
> :> (see /usr/ports/sysutils/cpdup).
> :
> :we use rdist on our network to keep our production servers in sync...we
> :tend to avoid 'nfs traffic' as much as possible...
> :
> :Marc G. Fournier   ICQ#7615664   IRC Nick: Scrappy
> 
> I've never trusted rdist for exact mirroring.  I remember trying to use
> it at BEST and it not getting everything right, though I can't remember
> exactly what it didn't get right... probably things like devices and
> hardlinks.  I wound up taking the 'stat' hit and having the clients
> scan the disk hierarchy for changes, and making sure the NFS server
> could handle it.  But you do not have to do things that way -- for example,
> the server could keep track of the changes itself and send a list to
> the client which the client then copies via NFS.

There is also rsync which can push/pull data, handles devices
and hard links correctly and which also works through ssh.
Especially the latter is a nice feature, because I had to do
some live mirroring once over untrusted networks. Getting
secure file transfering to work was quite easy using
ssh/rsync. Hardcore rdist users will miss the flexibility of
their rdist.conf, but most applications can be implemented
through some clever shell scripting.

-- 

  Regards,

Sascha Schumann
 Consultant


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 2 hours to compile mysql?

2000-01-03 Thread Sascha Schumann

On Mon, Jan 03, 2000 at 07:23:36PM -0700, Sasha Pachev wrote:
> Leif Neland wrote:
> > 
> > > The reason for this is that some gcc optimizations stages takes
> > > exponentially more memory when compiling big functions.
> > > bison produces one big function for the grammar parsing and its
> > > this that takes a long time to compile;  To compile sql_yacc.cc quickly
> > > on Intel, you nead at least 160M of free ram.  On a PentiumII 400mz with 256M
> > > ram, it takes 11 seconds to compile sql_yacc.o.  Having to use swap
> > > can easily make things 1000 times slower
> > >
> > 
> > Is amount of ram available (portably) to configure?
> > So configure could decide to use --low-memory by itself? Allowing
> > overrides, naturally.
> > 
> > Leif
> > 
> 
> There is actually a method to portably guess how much RAM your have available
> from configure -- just write a small C program that will keep malloc()-ing until
> it gets an error, but I do not think it is worth the effort.

There is also no guarantee that the allocated memory will be
available for real use (keyword resource overcommitting).

-- 

  Regards,

Sascha Schumann
 Consultant


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Your misleading, no LYING message to me

2000-01-02 Thread Sascha Schumann

On Sun, Jan 02, 2000 at 09:59:28PM -0600,  wrote:
> He is just expressing his point. From what I can tell someone removed him
> from the list with no reason and now he is angry. I probably would be too.

That does not excuse his style of communication. Shouting and
calling people names is no solution. It will damage the
relationship between the involved parties and will make an
agreement among them impossible. You can express emotions,
but please do it in a civilized and controlled way.

I usually recommened the following books to disagreeing
parties. They are easy to read and tell you much about
communication.

Getting to Yes, by Fisher and Ury, ISBN 0140157352
(Focusing on Interests, not on Positions)

Getting Past No, by Ury, ISBN 0553371312
(Negotiating Your Way from Confrontation to Cooperation)

-- 

  Regards,

    Sascha Schumann
 Consultant


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message