public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27528] compiling linux kernels 2.6.16.14/15 2.6.17-rc3 on powerpc (7450) get error on long exixting code
Date: Wed, 10 May 2006 20:17:00 -0000	[thread overview]
Message-ID: <20060510201735.32515.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27528-11706@http.gcc.gnu.org/bugzilla/>



------- Comment #8 from malitzke at metronets dot com  2006-05-10 20:17 -------
Well Fellas: Either have the Steering Committee revise the
Invitation to participate in testing; quoted iselectively below.
Or,have a member from the Steering Committe ask me to refrain
from further participation. I, for one, am no longer willing
to be at the receiving end of snide comments from people who
can not admit that, volunteering or not, are talking through 
their hats.

I am over 70 years of age and have come to my expertise (which
is not in compilers) the hard way. I started with plugboards
and worked my way up to real time assembly systems programming
(telephone Central Office switches and dispatching systems).
The proof of any programming effort is for the hardware to
generate the right output to control other hardware or to
be comprehensible by human beings.   

Now to the specifics:

>  This page describes regular efforts to test GCC thoroughly,
>  plus ideas for additional testing by volunteers who have
>  machine cycles to spare.

You might not believe it, but I have a router-firewall, a 
MAC (dual 800 Mhz G4's), a Pentium 3 server (four 550 Mhz
Pentium 3 with 2Gbyte error correcting memory an 130 Giga 
byes of SCSI) assorted other machines all running with
software entirely compiled with gcc-4.1 and gcc-4.2. I only
report to gcc.gnu.org what I consider important problems.
In this specific case I just eliminated the __FUNCTION__
part from bug.h (asm-powerpc) and I am writing this with
kernel-2.6.17-rc3 as compiled by the current gcc-4.2 on
the MAC.

>  Perform regular builds and testing of current GCC sources
>  that are not already being reported regularly.

Compiling everything but Ada and running the full test
suite now takes 8.5 hours on a ~800 Mhz pentium 3. There
is realy no publicly available Ada source. I, personally
do not care for Java, but some source packages require
it and sun is apparently no coming out with new releases for 
the powerpc series (competition for server sales) I check
the test suite output to see if that particular gcc is to
be my current production compiler for either pentium3 or
powerpc.

>  If the operating system kernel you use is normally compiled
>  with GCC, try building it with the current sources;
>  such as a release branch, use the newly built kernel for
>  running further GCC tests.

I am a user of compilers (not only gcc) and not a compiler
builder. The four or five problems I reported (and caused 
changes in gcc) sofar were not evidenced by the test suite.

>  Build and test applications that are important to you;
>  investigate and report any problems you find.

>  Build and test packages that are normally available on
>  your platform and for which you have access to source.a

I have about 40 Gigabyte of source code (no games, no IRC,
no themes or their engines, no music or downloading software,
as little Java as possible, and no Pascal).  This is really
software for workstation use. 

Regarding __func__ C99 declares it a "predefined identifier"
and "Like keywords, predefined identifiers must no be
defined by programmers." I am not asking that it becomes
part of GCC. however it should made clear that it and 
certainly __FUNCTION__ are no longer supported.

Regarding __LINE__, __FILE__, __DATE__, etc are required
as per Standard C. Again, the GCC community can state
that it is no honoring that particular requiremnt. However,
the GCC comunity can not unilaterally abrogate that
requirement. The trigraphs come to mind. These are 
probably matters for the Steering Committee.


-- 

malitzke at metronets dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27528


  parent reply	other threads:[~2006-05-10 20:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  2:44 [Bug c/27528] New: " malitzke at metronets dot com
2006-05-10  3:05 ` [Bug c/27528] " malitzke at metronets dot com
2006-05-10  4:04 ` [Bug middle-end/27528] " pinskia at gcc dot gnu dot org
2006-05-10  5:24 ` pinskia at gcc dot gnu dot org
2006-05-10  5:30 ` pinskia at gcc dot gnu dot org
2006-05-10 14:44 ` malitzke at metronets dot com
2006-05-10 14:56 ` dje at gcc dot gnu dot org
2006-05-10 15:06 ` pinskia at gcc dot gnu dot org
2006-05-10 20:17 ` malitzke at metronets dot com [this message]
2006-05-10 20:41 ` pinskia at gcc dot gnu dot org
2006-06-14 15:09 ` hp at gcc dot gnu dot org
2006-06-14 15:09 ` hp at gcc dot gnu dot org
2006-06-15  3:26 ` malitzke at metronets dot com
2006-06-15 17:15 ` hp at gcc dot gnu dot org
2006-06-15 23:03 ` malitzke at metronets dot com
2006-06-15 23:03   ` Andrew Pinski
2006-06-15 23:07 ` pinskia at physics dot uc dot edu
2006-10-27  5:24 ` pinskia at gcc dot gnu dot org
2006-11-03 13:23 ` rsandifo at gcc dot gnu dot org
2006-11-03 13:27 ` hp at gcc dot gnu dot org
2006-11-03 13:30 ` rsandifo at gcc dot gnu dot org
2006-11-09  9:34 ` rsandifo at gcc dot gnu dot org
2006-11-11  9:47 ` rsandifo at gcc dot gnu dot org
2006-11-11  9:53 ` rsandifo at gcc dot gnu dot org
2006-11-11  9:54 ` rsandifo at gcc dot gnu dot org
2006-12-01  1:07 ` chaoyingfu at gcc dot gnu dot org
2007-01-10 19:14 ` [Bug middle-end/27528] [4.2/4.3 Regression] " pinskia at gcc dot gnu dot org

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=20060510201735.32515.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).