Peter S. Mazinger wrote:
> --- gcc-4.0.2/gcc/config/m68k/linux.h.mps 2006-01-08 23:02:06 +0100
> +++ gcc-4.0.2/gcc/config/m68k/linux.h 2006-01-08 23:03:02 +0100
> @@ -85,6 +85,11 @@
> LINUX_TARGET_OS_CPP_BUILTINS(); \
> builtin_define_std ("mc68000"); \
> buil
Bernardo Innocenti wrote:
>> --- gcc-4.0.2/gcc/config/m68k/linux.h.mps2006-01-08 23:02:06 +0100
>> +++ gcc-4.0.2/gcc/config/m68k/linux.h2006-01-08 23:03:02 +0100
>> @@ -85,6 +85,11 @@
>> LINUX_TARGET_OS_CPP_BUILTINS(); \
>> builtin_define_std ("mc68000"); \
>>
Diego Novillo wrote:
On Tuesday 03 January 2006 12:17, [EMAIL PROTECTED] wrote:
how to keep my branch updated with the mainline?
The easiest way is using svnmerge.py (included in SVN's contrib directory).
There's documentation in the GCC wiki: http://gcc.gnu.org/wiki/SvnBranch
Just tried
Bernd Schmidt <[EMAIL PROTECTED]> wrote:
> Just tried these instructions on the reload-branch, and it doesn't
> appear to be working as documented:
>
> [EMAIL PROTECTED]:/local/src/egcs/reload-branch> svnmerge.py init
> property 'svnmerge-integrated' set on '.'
This was the correct command to do,
This was the correct command to do, assuming that you *never* merged your
branch since its original creation. I inspected the history of the branch
(through 'svn log') and it seems this assumption is correct.
Yes.
Anyway, I have fixed the bug in svnmerge and attached a new version for you
in t
One additional question, suppose I don't want to merge a huge number of
revisions in one go, and I do
svnmerge.py merge -r a-small-list-of-revisions
svn diff ;; to verify everything is OK
Do I then have to commit the merge so far before running svnmerge.py
again, or can it get all the infor
Bernd Schmidt <[EMAIL PROTECTED]> wrote:
>> Anyway, I have fixed the bug in svnmerge and attached a new version for
you
>> in this mail.
>
> Thanks for the quick fix. This seems to be working now ("svnmerge.py
> avail" gives me a rather enormous list of revision numbers).
Yes. It'll take some ti
Bernd Schmidt <[EMAIL PROTECTED]> wrote:
> One additional question, suppose I don't want to merge a huge number of
> revisions in one go, and I do
>svnmerge.py merge -r a-small-list-of-revisions
>svn diff ;; to verify everything is OK
>
> Do I then have to commit the merge so far before ru
Bernd Schmidt <[EMAIL PROTECTED]> wrote:
> One additional question, suppose I don't want to merge a huge number of
> revisions in one go, and I do
>svnmerge.py merge -r a-small-list-of-revisions
>svn diff ;; to verify everything is OK
>
> Do I then have to commit the merge so far before ru
Giovanni Bajo wrote:
Bernd Schmidt <[EMAIL PROTECTED]> wrote:
One additional question, suppose I don't want to merge a huge number of
revisions in one go, and I do
svnmerge.py merge -r a-small-list-of-revisions
svn diff ;; to verify everything is OK
Do I then have to commit the merge so f
Bernd Schmidt <[EMAIL PROTECTED]> wrote:
>>> One additional question, suppose I don't want to merge a huge number of
>>> revisions in one go, and I do
>>> svnmerge.py merge -r a-small-list-of-revisions
>>> svn diff ;; to verify everything is OK
>>>
>>> Do I then have to commit the merge so far
* Christophe Jaillet ([EMAIL PROTECTED]) [20060109 20:00]:
> in file 'bt-load.c', in function 'augment_live_range', some memory is
> xmalloc'ed. It seems to be possible to never free it, if all the first tests
> are true.
This is now PR 25739.
Philipp
Hi.
On your online docs web page (http://gcc.gnu.org/onlinedocs/), all the links
for GCC 3.4.5 GNAT User's Guide bring up a message that the page cannot be
found.
The paths for the links look consistent in their format to other links that
work, which makes me wonder if the docs just aren't there
In short, you are proposing that instead of linking an executable, it
be made into a bunch of shared libraries. The function calls between
these shared libraries be arbitrated by a "dispatcher" which can
dynamically reroute function calls.
There already exists a technique to do this if you
I getting the following warning with unsigned long long world_wide_name;
(scsi_buf.h).
warning : integer constant is too large for "long" type.
Is there a swich I need to add?
I am just using: gcc -o test test.c
Thanks!
--
View this message in context:
http://www.nabble.com/ggc-3.3.2-
On Tue, Jan 10, 2006 at 10:28:26AM -0800, Chris Miller wrote:
>
> On your online docs web page (http://gcc.gnu.org/onlinedocs/), all the links
> for GCC 3.4.5 GNAT User's Guide bring up a message that the page cannot be
> found.
>
> The paths for the links look consistent in their format to other
Hello,
whats the status of -fstack-usage?
Will it output the real or worst case stack usage?
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
One more question (I'm experimenting... excuse the stupid questions but
I'd rather not accidentally mess up the branch). What I did now was, first,
~/svnmerge.py merge -r 96659-96679
just to get started, then
~/svnmerge.py merge -F -r 96681,,9
with the list of numbers cut&pasted fro
Snapshot gcc-3.4-20060110 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/3.4-20060110/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 3.4 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
Making slow progress...
I now have libstdc++ compiled as "standalone" I am down to "free",
"malloc", "abort", and "_restf4". free and malloc I can hook up to
net_free and net_malloc. abort I can hook up to panic. Its the
_restf14 that gets me.
It is pulled in from unwind_dw2.o of libg
Bernd Schmidt <[EMAIL PROTECTED]> wrote:
> One more question (I'm experimenting... excuse the stupid questions
> but I'd rather not accidentally mess up the branch). What I did now was,
> first,
>
>~/svnmerge.py merge -r 96659-96679
>
> just to get started, then
>
>~/svnmerge.py merge -
21 matches
Mail list logo
