public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Grant <emailgrant@gmail.com>
Subject: Re: [gentoo-user] gcc upgrade - rebuild everything?
Date: Thu, 21 Oct 2010 23:07:50 +0200	[thread overview]
Message-ID: <201010212307.50617.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <AANLkTimoL2OFj9dAw1y+1BbNOX1F8xm7tVV26At=7dgL@mail.gmail.com>

Apparently, though unproven, at 21:58 on Thursday 21 October 2010, Grant did 
opine thusly:

> I just upgraded from gcc-4.4.3-r2 to gcc-4.4.4-r2 and I'm wondering if
> I really need to rebuild everything as it says in the guide:
> 
> http://www.gentoo.org/doc/en/gcc-upgrading.xml

No, you do not need to do this. The document is over-reaching (see below)

I ran a mixture of 4.4.3 and 4.4.4 for ages, completely trouble-free.

> If not, when is it necessary?

When you have an ABI change in the code generated by the compiler. In other 
words, when code generated by this version is incompatible with code generated 
by that version, and you have both on the same system. This has not happened 
for a long time in gcc-land.

Now, about that official doc. Your question comes up with unbelievable 
regularity and every time the poster references that doc. But it is not 
necessary to do what the doc says, and a long time ago I think I figured it 
out.

The author's intention is less to give you the absolute complete total 100% 
truth that will always work out just fine, and more to reduce the amount of 
clutter in his inbox or on b.g.o.

The rules about how to detect when a rebuild of world is needed are complex 
and most readers simply will not understand them - they don't understand 
compiler internals (how many people DO?). But if you tell people to just 
rebuild world every time, and weird funny lurking problems are likely to just 
get fixed as a side effect, no real harm is done. Does it hurt the author? No. 
Does it reduce the amount of bugs he has to deal with on the rare occasion it 
is needed? Yes.

What does the user lose? Nothing much, more cpu cycles get used, more bits 
flip on a disk, your video card gets a work out scrolling all that text. Will 
you waste time? Yes. Will you break stuff? No.

So rebuild world if it makes you feel better. But you don't need to this time. 
The authors of gcc will certainly notify the entire world and it's dogs when 
you do need to.

-- 
alan dot mckinnon at gmail dot com



  parent reply	other threads:[~2010-10-21 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 19:58 [gentoo-user] gcc upgrade - rebuild everything? Grant
2010-10-21 20:09 ` Dale
2010-10-21 20:12 ` Alex Schuster
2010-10-21 20:12 ` Paul Hartman
2010-10-21 21:07 ` Alan McKinnon [this message]
2010-10-22 16:31   ` Grant
2010-10-21 21:57 ` [gentoo-user] " Nikos Chantziaras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201010212307.50617.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=emailgrant@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox