Re: WTF?

[Ben Elliston]

On Wed, 2009-11-25 at 15:17 -0500, Kaveh R. GHAZI wrote:

> Finally, we have a process for reverting a patch.  If anyone wants to
> revert some part, it needs to be followed.  Otherwise *that* would be
> breaking the rules...

Won't reverting the patch just attribute all of the lines to the
username of the reverter?  Losing the svn blame facility is a serious
regression to my mind.

Ben

Re: help regarding instruction scheduling in gcc - dfa(deterministic finite automaton)

[Ben Elliston]

On Sun, 2009-10-18 at 08:17 -0700, ddmetro wrote:

> 1. The starting point of generation of dfa(by reading md files) is
> 'genautomata.c'. When is the main() method of 'genautomata.c' called?

genautomata is compiled into the build/genautomata binary in your build
tree.  It is then invoked during the build process.

> 2. How and in what datastructure - is the dfa generated by 'genautomata.c'
> persisted between two method calls - one of main() method of genautomata.c
> and another of toplev_main() method of toplev.c 

The DFA is produced by genautomata and left behind in generated source
files in the build directory .. see insn-automata.c and insn-automata.h
as a starting point.  These files are then compiled into GCC.

Cheers, Ben

Re: problems with gcc installation

[Ben Elliston]

On Thu, 2009-10-15 at 01:16 -0700, yzysea wrote:

>   I need to intall gcc-2.5.8 on opensolaris. In the "make" step, I get  the
> following message:

This is the GCC development list, not a list for answering questions
about how to compile up and use GCC.  Please take your question to the
gcc-h...@gcc.gnu.org list, which is the more appropriate list.

Why on earth do you want to compile GCC 2.5.8?  It was released over 15
years ago.

Cheers, Ben

Re: delete dead feature branches?

[Ben Elliston]

On Wed, 2009-10-14 at 08:33 +0200, Michael Matz wrote:

> So, why not just move them to dead-branches now, and be done with it?

OK, your argument has convinced me. :-)

Cheers,
Ben

Re: delete dead feature branches?

[Ben Elliston]

On Tue, 2009-10-13 at 03:05 +0200, Michael Matz wrote:

> I don't think we should necessarily limit ourself by bugs in foreign tools 
> if it reduces useful information.  What about a new top-level directory 
> dead-branches/, not under branches/ but parallel to it?  Should be easy to 
> exempt from git-svn handling, shouldn't it?

I found that svn log works well if you do this:

  svn log svn+ssh://b...@gcc.gnu.org/svn/gcc | less

The important thing is to make sure that the log message carefully
describes the name of the branch when it is deleted, so that one can
search the log output to find it.

I deleted a personal branch from 5 years ago and have added the revision
number of the delete commit to the branch description in svn.html.

Would these two conventions suffice?

Ben

Re: delete dead feature branches?

[Ben Elliston]

On Fri, 2009-09-25 at 16:55 +, Joseph S. Myers wrote:

> Do we believe any future conversion to another version control system 
> (that might have a more structured notion of what is a branch than it 
> simply being a directory used in a certain way) would continue to make the 
> history of such branches readily available?

If that happens to be true with some future version control system,
couldn't we restore the deleted branches before running whatever
conversion tool exists?

Ben

-- 
Ben Elliston 
Australia Development Lab, IBM

Re: how to get the .dfa output file in gcc

[Ben Elliston]

On Sat, 2009-10-03 at 11:37 -0700, ddmetro wrote:

> 1. In the initiate_automaton_gen() function of 'genautomata.c', initialize
> the v_flag variable to 1 i.e., v_flag = 1;

It should not be necessary to do this.  Can you retry with the .md
syntax?

Ben

Re: LTO merge - free_lang_data

[Ben Elliston]

On Mon, 2009-08-17 at 12:01 -0400, Diego Novillo wrote:

> Since the patch is rather large and it affects the other LTO
> merge activities, I've been thinking about ways of making it
> easier and avoid conflicts:
> 
> 1- Keep working on my local tree; combining both free_lang_data and
>early debug generation.
> 
> 2- Add free_lang_data to trunk with a gate function that only
>triggers it if -g is missing.
> 
> 3- Add free_lang_data to trunk with a gate function that enables
>it only if a special flag is given on the command line.

I agree with Richard: #2.

Ben

Re: Difference between Windows and Linux GCC compiler

[Ben Elliston]

Hi.

> I'm interested to know what is the difference in programming using MS
> Visual C++ on Windows and using the GCC compiler on Linux, i.e. what
> are some of the things I can do on Visual C++ that won't compile/run
> on Linux, and vice versa.

This mailing list is for discussing GCC development, not questions about
using GCC or porting software to/from Linux.  Please try asking this
question on the gcc-h...@gcc.gnu.org list instead.  Thanks,

Ben

Re: Porting GCC 4.4.0 to interix

[Ben Elliston]

On Thu, 2009-07-30 at 23:58 +0100, Robert Oeffner wrote:

> Until now there is no compiler available for interix that supports OpenMP 
> and that's what I'm after. As libgomp in GCC so far isn't targeting interix 
> I have made some changes to libgomp in my copy of the GCC 4.4.0 
> distribution.

libgomp relies on pthreads (well, at least in the only current
implementation of that library).  Which pthread library are you using?
Does Interix supply one?

Ben

Re: [testsuite] Executing testcases under wine

[Ben Elliston]

> I'm trying to run the GCC testsuite for the mingw target, on a i686- 
> darwin host. The cross compiler builds fine, and I have wine  
> installed, so I'd like testsuite executables, once compiled, to simply  
> run under wine (that means, instead of running "PR10431.exe", running  
> "wine PR10431.exe"). I've found a crude way to do this by patching my  
> system dejagnu config file (/usr/share/dejagnu/config/unix.exp):

I think the right way to handle this is to treat wine as a simulator.
Take a look at some of the existing dejagnu board definitions to see how
to do this.  Perhaps something like:

  set_board_info sim xt-run

Cheers, Ben

Re: GPL (probably a FAQ)

[Ben Elliston]

This thread is off-topic for the GCC mailing list.  Please follow up on
gnu.misc.discuss or some other suitable forum.

Thanks,
Ben

Re: increasing the number of GCC reviewers

[Ben Elliston]

On Tue, 2009-06-09 at 21:13 +0200, Basile STARYNKEVITCH wrote:

> This is precisely my point. It should be perfectly acceptable that some 
> people be authorized to approve some few patches without understanding 
> the whole of GCC, and even without knowing all of it.

I sympathise with this point of view, Basile.  Over the time I have
worked on GCC, there has been a lot of modularity improvements and
improving the robustness of interfaces throughout the compiler.  If this
continues, it should be possible to understand changes in more
isolation.  While there will always be consequences that need to be
understood, but that should not apply to every change.

Ben

Re: increasing the number of GCC reviewers

[Ben Elliston]

On Tue, 2009-06-09 at 19:00 +0100, Andrew Haley wrote:

> I think it's a much better idea to contact Fred (or Freda, for that matter)
> Bloggs to ask them if they want to maintain reload.  :-)

Wouldn't it be Alan Smithee to maintain reload? :-)

Ben

Re: Any comment about the replacement of gcc news?

[Ben Elliston]

On Wed, 2009-06-03 at 16:33 +0800, Eric Fisher wrote:

> Sorry, I hope it's not an offensive or boring topic.

No, just off-topic.  This list is for developing gcc, not plotting our
demise.

Cheers, Ben

Re: Do we have optimizations to reduce cache miss?

[Ben Elliston]

> I just want to ask whether we have any special pass to reduce cache
> miss? Or any idea or branch to enhance it.

There are various data layout optimisations.  There is also -Os ;-)

Ben

Re: Type-punning warnings [was Re: PATCH: silence warnings in unwind-dw2-fde.c]

[Ben Elliston]

On Tue, 2009-05-19 at 14:57 +0200, Richard Guenther wrote:

> The patch is ok.

I fell off the Cc: list, but I assume you are talking to me. :-)

Thanks,
Ben

Re: new warnings building cp-demangle.c

[Ben Elliston]

On Mon, 2009-05-18 at 17:40 -0700, H.J. Lu wrote:

> We have
> 
> enum gnu_v3_ctor_kinds {
>   gnu_v3_complete_object_ctor = 1,
>   gnu_v3_base_object_ctor,
>   gnu_v3_complete_object_allocating_ctor
> };
> 
> What does
> 
> (kind < gnu_v3_complete_object_ctor
>  && kind > gnu_v3_complete_object_allocating_ctor)
> 
> try to check? It looks like a typo to me.

Right--that was my point.

Ben

new warnings building cp-demangle.c

[Ben Elliston]

Hi Ian

In the last couple of days, I have started seeing the following warnings
when building target-libiberty:

/home/bje/source/gcc-clean/libiberty/cp-demangle.c:723: warning: logical ‘and’ 
of mutually exclusive tests is always false
/home/bje/source/gcc-clean/libiberty/cp-demangle.c:742: warning: logical ‘and’ 
of mutually exclusive tests is always false

The code around line 723 is:

  if (p == NULL
  || name == NULL
  || (kind < gnu_v3_complete_object_ctor
  && kind > gnu_v3_complete_object_allocating_ctor))
return 0;

(and similarly for line 742).  A bug?

Cheers, Ben

Re: Request about adding a new micro support

[Ben Elliston]

> How can I add to gcc support for a 8-bit micro (Harvard architecture)?
> An RTFM link would be really appreciated. :-)

This question really belongs on the gcc-h...@gcc.gnu.org mailing list.
The GCC internals manual can be found at:

  http://gcc.gnu.org/onlinedocs/gccint

Ben

Re: Documentation on running dejagnu with qemu?

[Ben Elliston]

On Tue, 2009-04-28 at 14:52 -0700, Doug Kwan (關振德) wrote:

> I would like to run the testsuite using qemu as the gdb simulator does
> not support newer ARMs.  However, there does not seems to be any good
> documents on that topic.  Could someone give me a pointer or two?

If you are running a full operating system image in qemu, the easiest
way is to set it up with an FTP/telnet server (or SSH server) so that
you can treat the system as a remote Unix system.

It would probably be best to take follow-ups to the dejagnu list.

Cheers, Ben

Re: new offset outside bounds of constant string warning

[Ben Elliston]

On Manuel's recommendation, I have backed out revision 145102 for the
time being.  If someone wishes to have another go at it, the code is in
svn.

Cheers, Ben

--
Ben Elliston 
Australia Development Lab, IBM

new offset outside bounds of constant string warning

[Ben Elliston]

Hi HJ

According to svn annotate, it was you who authored the new 'offset
outside bounds of constant string warning' warning in GCC (well, I think
so, anyway).  The compiler now complains about some code in the C++
demangler:

/home/bje/source/gcc-trunk/libiberty/cplus-dem.c:2651: warning: offset ‘3’ 
outside bounds of constant string

I tracked this down to the definition of strspn used on my Linux system:

#   define strspn(s, accept) \
  __extension__   \
  ({ char __a0, __a1, __a2;   \
 (__builtin_constant_p (accept) && __string2_1bptr_p (accept) \
  ? ((__builtin_constant_p (s) && __string2_1bptr_p (s))  \
 ? __builtin_strspn (s, accept)   \
 : ((__a0 = ((__const char *) (accept))[0], __a0 == '\0') \
? ((void) (s), 0) \
: ((__a1 = ((__const char *) (accept))[1], __a1 == '\0')  \
   ? __strspn_c1 (s, __a0)\
   : ((__a2 = ((__const char *) (accept))[2], __a2 == '\0')   \
  ? __strspn_c2 (s, __a0, __a1)   \
  : (((__const char *) (accept))[3] == '\0'   \
 ? __strspn_c3 (s, __a0, __a1, __a2)  \
 : __builtin_strspn (s, accept))  \
  : __builtin_strspn (s, accept)); })

Is this something you can fix?

Thanks, Ben

Re: Question about top-level configure code and in-tree builds

[Ben Elliston]

On Fri, 2009-04-10 at 23:56 -0400, Kaveh R. GHAZI wrote:

> Ah, but cake is only easy when someone else bakes it. :-)

While you're baking, Kaveh :-) could you see if your patch could also
fix:

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

Thanks, Ben

Re: The gcc-in-cxx branch now completes bootstrap

[Ben Elliston]

On Sat, 2009-04-11 at 22:37 +0200, Thomas Neumann wrote:

> Is there any reasonably simple way to find out why the C++ version is 
> slower? I can use something like oprofile, of course, but I thought
> gcc can somehow give statistics about its internal times, which might
> be more useful for a first approximation.

Try using -ftime-report.

Ben

Re: Intermittent/non-reproducible gcc testsuite failures

[Ben Elliston]

On Tue, 2009-04-07 at 23:45 -0700, Michael Eager wrote:

> I'm running the gcc test suite on powerpc-unknown-eabisim
> on the trunk and I get results which are different from
> one run to the next.  When I run the failing tests by
> hand, all pass.  Mike Stein also has noted that some of
> the tests are intermittent failures.

> Does anyone have any suggestions on how to get one of
> these tests to fail consistently, or a different approach
> to finding the cause of the intermittent failures?

There are two (or three?) sources of interittency here, and one of them
is the testsuite harness itself.  One thing you could do to try and
narrow it down is to run *just* the test cases you are seeing
intermittency in using RUNTESTFLAGS=foo.exp=bar.c a dozen times and see
if the results are stable.

Cheers, Ben

Re: GCC 4.4.0 Status Report (2009-03-13)

[Ben Elliston]

On Sun, 2009-03-22 at 18:30 -0500, Gabriel Dos Reis wrote:

> And there certainly are successful projects using a subset of C++ too.
> Whether you have not seen them is, well, a different matter :-)

I could well even be using such software--I'm just not aware of it. :-)

Can you give some indication of how the subset is enforced?

Ben

Re: Playing with gcc-testresult results

[Ben Elliston]

On Sat, 2009-03-21 at 18:09 +0100, Steven Bosscher wrote:

> Interestingly, the results show that no compiler has more test results
> posted than GCC 4.4.0, which hasn't even been released yet! It looks
> like there are many results from ia64 and x86_64 automatic testers
> these days. Also interesting is that some of the primary targets have
> almost no posted test results :-(

Perhaps we need to reassess the list of primary targets, then?

Cheers, Ben

Re: GCC 4.4.0 Status Report (2009-03-13)

[Ben Elliston]

On Sun, 2009-03-22 at 17:43 -0500, Gabriel Dos Reis wrote:

> Well, the request was not about the full gamut of C++, but rather
> a subset.  And the time of the discussion, I thought the subset
> was quite conservative. Every programming language can
> be abused -- and I don't think I've made an exception for C++.

GCC would not be the first project (free, or proprietary) that I have
seen attempt to use a subset of C++.  I don't think I've ever seen this
succeed.  Inevitably, use of certain features crawl in when there is no
cleaner way to achieve something and then precedent can be used as an
argument for further use.

I'm a bit sceptical.

Ben

Re: Is there any flags to disable warning and/or errors given by GCC 4.3.3?

[Ben Elliston]

Hi.

This question is not really suitable for the GCC mailing list; this is a
list for discussing GCC development.  The right place to send such
questions is gcc-h...@gcc.gnu.org.  Thanks.

>I am not able compile my project with GCC 4.3.3 C++. My project 
> was compiled by GCC 4.1.x. 

It's a common situation.

>Is there any flags to disable warning and/or errors given by GCC 
> 4.3.3?

You can do that using -Wno-, but:

>I should remove and/or change code to eliminate warning and/or
> error?

You should fix your code so that it complies with the C++ standard (that
GCC 4.3 will be more strictly enforcing).

Cheers, Ben

Re: GCC C FRONT END EXPLANATION

[Ben Elliston]

Ah, good, a duplicate question that I just answered. :-)
See http://gcc.gnu.org/ml/gcc/2009-03/msg00554.html

Ben

Re: gcc c grammar

[Ben Elliston]

On Thu, 2009-03-19 at 23:29 -0300, Eduardo Cruz wrote:

> I thought gcc used bison as a syntax analyser, but when I saw the gcc
> c-parser source code I realized that it didn't use bison.
> I read in the gcc mailist that gcc now has a recursive descent parser.

That's right.

> Do you have any document that contains the grammar implemented in gcc 
> c-parser?

Yes, the C standard!

> It would be easier to make the proprer changes in the grammar if I
> have this document, because I won't have to understand the grammar
> reading the source code.

The C parser source code is annotated with the grammar to help you
understand it.  For example, see the large comment that appears before
c_parser_declspecs in c-parser.c.

Cheers, Ben

Re: missing return statement

[Ben Elliston]

(Note that this is really a question for gcc-help.)

On Thu, 2009-03-12 at 23:42 +, Nathan Ridge wrote:

> Why does gcc not give an error about this?
> If I compile with "-Wall", it will give a WARNING saying
> "control reaches end of non-void function".

You can turn this warning into an error with -Werror.

Ben

Re: The gcc-in-cxx branch now completes bootstrap

[Ben Elliston]

On Mon, 2009-03-09 at 21:25 -0700, Ian Lance Taylor wrote:

> > Also, is there any significant difference in bootstrap times?
> 
> I haven't actually measured, but subjectively bootstrap does seem to
> take longer.

A subjective assessment was all I was interested in.

Thanks,
Ben

Re: The gcc-in-cxx branch now completes bootstrap

[Ben Elliston]

> I'm curious whether there are any detectable differences in the resulting
> compiler when built with g++ rather than gcc.  E.g. testsuite regressions,
> changes in the speed or size of cc1, etc.  Also, is cc1 linked with
> libstdc++.so ?  Stuff like that.

Also, is there any significant difference in bootstrap times?

Ben

Re: [Ada] Fix Windows merge glitch

[Ben Elliston]

On Sat, 2009-02-28 at 18:31 +0100, Eric Botcazou wrote:

>   * gcc-interface/Makefile.in (cygwin/mingw): Revert accidental
>   EH_MECHANISM change in r130816.

I've seen a few ChangeLog entries like this of late, so thought I would
raise something: is it now accepted practice to mention SVN revision
numbers in ChangeLog entries?  I know it is convenient to do it, but (a)
we might switch version control systems again, and (b) people have been
known to work with FSF trees off-line or in other version control
systems where the FSF repository is not accessible.

Just a thought,

Ben

Re: make install fails to create gcc ?

[Ben Elliston]

> In any case . .the gcc binary is missing in action .. did make install
> fail in some weird way ?

Possibly, but make should have failed also.

Ben

Re: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)

[Ben Elliston]

On Tue, 2009-02-03 at 01:59 -0500, Sean Callanan wrote:

> Our plugins do not break when switching compiler binaries.  In fact, I  
> have had plug-in binaries that perform very simple tasks work fine  
> when switching (minor!) compiler releases.

Thinking about this made me realise that the plugin framework will
require special consideration for utilities like ccache and distcc.
ccache checksums (or at least stats) the cc1 binary to decide whether a
cached object file is valid.  If you change a plugin, the cc1 binary
won't change, but the generated code probably will.

Ben

Re: GCC Plug-in Framework ready to port

[Ben Elliston]

On Sun, 2009-02-01 at 14:26 -0500, Diego Novillo wrote:

> Yes, that's the path I was describing; plugins distributed with GCC.
> I don't expect we'll have more than a small number of them.  Mostly as
> examples.

The usual problem with example plugins is that they stop working.  It
would be nice if they were built and tested as part of the usual build
process (and `make check'), but not installed.

Ben

incorrect license on some gcc/*.c files?

[Ben Elliston]

After reading about the new runtime license, I did some grepping through
the gcc/ directory to see how many files would need updating.  I was
surprised to discover three files that are part of GCC proper, but are
still under GPLv2.  Shouldn't these all be GPLv3?

M  tree-parloops.c
M  ipa-struct-reorg.c
M  ipa-struct-reorg.h

If so, I have a patch and will submit it.

Ben

Re: GCC RES: Restrictive Exception Specification: 0.1 - Alpha. Feedback Request.

[Ben Elliston]

Hi Simon

> I recently (on 18/12/2008) mailed a GCC patch to this mailing list,
> but I went on holiday after and have only just arrived back. I
> probably should have asked for some feedback then.

Thanks for taking the time to describe your work in the right amount of
detail.  I think you need a C++ maintainer to indicate their willingness
to accept your patch in principle, and then in final form.

In the meantime, for such a significant patch, you are going to need to
get your copyright assignment paperwork cleared up before the patch can
be accepted.  Do you have one yet?

Cheers, Ben

Re: cross-compilation, deprecated option and libgcc

[Ben Elliston]

On Mon, 2009-01-26 at 14:19 +0100, Vincent R. wrote:

> 1) When I compile bootstrap gcc, I am using make all-gcc and make
> install-gcc and it seems it doesn't build libgcc anymore.

I think that's correct; make all-gcc just builds gcc these days.  To
build libgcc, you need to run make all-target-libgcc.  libgcc is no
longer built as part of gcc, but like any other of the target libraries.

It's best to do a make all and make install to avoid these hassles.  If
you want to keep the workload down, use --enable-languages to prune the
set of languages you support in your "bootstrap" compiler.  (Is there a
reason why you can't just build the cross using your system compiler?)

> So my first question is : For a bootstrap gcc do I need to build libgcc and
> in this case should I use make all and make install instead ?

Yes.

Cheers, Ben

Re: -fgraphite docs

[Ben Elliston]

On Mon, 2009-01-19 at 23:20 -0600, Sebastian Pop wrote:

> > Perhaps we should add a comment to common.opt to explain this?
> 
> Yes, we could apply this patch.

Looks good to me (and I think it qualifies as obvious) :-).

Thanks,
Ben

Re: -fgraphite docs

[Ben Elliston]

> > Is this an oversight, or are these options deprecated?
> 
> These options are intentionally not documented: they should not be
> used by programmers.

Perhaps we should add a comment to common.opt to explain this?

Ben

-fgraphite docs

[Ben Elliston]

Hi Sebastian

While reading through the Graphite code on the trunk, I noticed that
-fgraphite and -fgraphite-identity are no documented in doc/invoke.texi.
Is this an oversight, or are these options deprecated?

Ben

-- 
Ben Elliston 
Australia Development Lab, IBM

Re: Useless option parsing code in genautomata.c ?

[Ben Elliston]

> Now I just set v_flag to 1 manually in code to get the output, but I
> don't think it is a correct way.
> Anyone could tell me the correct way to output automata description,
> or help me to confirm this bug?

I don't think there is a bug.  What do you have in your define_automaton
directive?  Note that `-' is not required for these options.

Ben

Re: GCC 4.4 SNAPSHOT - BUILD ERROR

[Ben Elliston]

> Could someone help ?

Sure, there is even a mailing list: gcc-h...@gcc.gnu.org.  ;-)

> checking for suffix of object files... configure: error: in 
> `/home/meu/gcc-4.4-20090109/i686-pc-linux-gnu/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.

> I had never got a configure error before. Does someone know what I could do?

You need to take a look inside config.log; it will provide more details
about by the compiler failed to build those target objects.

Cheers, Ben

Re: gcc binary download

[Ben Elliston]

> I cannot find where to download gcc binary for Linux. Can you email me
> the link? It's so confusing in the http://gcc.gnu.org/ web site.

You should install gcc from your Linux distribution.  It will be far
easier.

Ben

Re: Installing GCC:Configuration (GCC-4.3.2)

[Ben Elliston]

On Tue, 2009-01-13 at 16:48 -0500, Franklyn Simon wrote:

> I download gcc-g++4.3.2 and uncompressed it along with the 
> prerequisites tar files in directory (/opt).  I am confused as to the 
> srcdir and objdir mentioned in Install GCC: Configuration.

You should take this question to gcc-h...@gcc.gnu.org.  This list is for
discussing GCC development, not installing GCC.  Thanks.

Ben

Re: gcc-4.3.2 build break at multilib glibc

[Ben Elliston]

> We need to use newlib. when to link with gcc ? whether using newlib will
> solve the above error ?

It will.  One way that you can get gcc to build newlib is to sym link
the newlib sources into the gcc tree.  The GCC build system will detect
this and build newlib for you:

cd gcc-4.3  # say
ln -s ../src/libgloss .
ln -s ../src/newlib .

Questions about building gcc should really be directed to
gcc-h...@gcc.gnu.org.

Cheers, Ben

Re: gcc-4.3.2 build break at multilib glibc

[Ben Elliston]

> Hi, I am trying to cross compile the gcc-4.3.2 for arm based dsp target.
> The following error occurs.

Building a cross-compiler for an embedded target requires a little bit
of know-how, usually best obtained from various guides on the net.  You
are getting these errors because you need a C library available.  It
should be possible for you to use newlib on this target.

Ben

Re: should make check be done "un-installed"?

[Ben Elliston]

> The implication of the opening statement of  http://gcc.gnu.org/ 
> install/test.html is that "make check" could (or even should) be done  
> before "make install"
> 
> Is this a correct interpretation of policy?

Yes, the testsuite is designed to test the compiler in the build tree.
It is also possible to test the compiler once it's installed, but this
is not the usual way of doing things.

Cheers, Ben

Re: g77 correct version

[Ben Elliston]

Hi Angela

> I would like to install a g77 on my version of Linux that is Scientific
> Linux SL-52-062608-i386.
> I tried to install 3 packages of g77 but I don't know what is the package
> suitable for me and my Linux version.

This mailing list is for discussing the development of gcc and g77,
rather than installing it.  You should probably address your question to
your distro vendor/community.

> Could you be so kind to indicate me the correct link for downloading g77
> package? And also I would like to know if I should install g77 as a root
> or as a simple user.

If your distro uses RPMs or deb packages, you will need to install them
as root.

Cheers, Ben

Re: [lto] Spurious failures in lto tests with -jN

[Ben Elliston]

> I've noticed some spurious failures in the lto tests (g++.dg/lto and
> gcc.dg/lto).  They only occur with -jN.  The symptom is an error
> message from ld complaining that a .lto.ltrans.o file is missing.  I
> think this is a bug in the lto.exp script because the tests work fine
> with -j1.

I assume you mean when running make -jN check-gcc?  Concurrency between
various .exp scripts should not cause you any problems, as each make
check is run in its own testsuite directory.

Ben

Re: Variadic template function full specialization.

[Ben Elliston]

> Following (bit weird ;-) code shows weird case of variadic template
> function specialization, however I am not sure it is legal, (atleast I
> haven't found any wording that would prevent such use):

This list is not really the place to discuss language issues (unless you
think you've found a bug in g++).  The [EMAIL PROTECTED] mailing list
is probably a better place to ask your question.

Cheers,
Ben

-- 
Ben Elliston <[EMAIL PROTECTED]>
Australia Development Lab, IBM

Re: Building GCC 4.3.2 on powerpc-yellowdog-linux-gnu

[Ben Elliston]

> I'm trying to build (natively) GCC 4.3.2 on a
> powerpc-yellowdog-linux-gnu. I have not yet managed to build it all
> ('make bootstrap') but I found out that each of the following changes
> (applied in the order specified) takes me further on:
> 
> -- insert '#include ' in libcpp/include/line-map.h:26 (to work
> around errors about undefined CHAR_BIT or UINT_MAX);
> -- insert '#include ' in gcc/real.h:29;
> -- add BOOT_CFLAGS='-DENABLE_DECIMAL_FLOAT=1
> -DENABLE_DECIMAL_BID_FORMAT=0' to 'make bootstrap' since these
> macros were not defined (this is stage 2);
> -- insert '#include ' in gcc/hard-reg-set.h:24;
> -- insert '#include ' in gcc/toplev.h:24;
> -- added -DHAVE_LIMITS_H to BOOT_CFLAGS;
> -- added -DHAVE_GAS_SHF_MERGE=0 to BOOT_CFLAGS;

You should not have to make any of these changes to bootstrap GCC 4.3.2
on a PowerPC GNU/Linux system.  We build these compilers regularly and
do not have to do this.

I think you're probably building GCC incorrectly.  Please follow-up with
a list of your steps to [EMAIL PROTECTED]

Thanks, Ben

-- 
Ben Elliston <[EMAIL PROTECTED]>
Australia Development Lab, IBM

Re: [PATCH]: bump minimum MPFR version, (includes some fortranbits)

[Ben Elliston]

On Mon, 2008-10-06 at 16:10 -0700, Kaveh R. Ghazi wrote:

> The last time this came up, the consensus was that we should not hard fail 
> the configure script even if the user would then be missing some mpfr bugfix 
> in the latest/greatest release.  That's why we have the minimum/recommended 
> split.

Doesn't this mean that we can then have two different versions of GCC
(as identified by gcc --version), linked with different mpfr libraries,
that may exhibit different behaviour?

Ben

Re: Extending a backend

[Ben Elliston]

> Load rt, s2(s18)
> Store s2(s18), rc
> 
> However after searching and reading a lot of documentation, I still cannot
> figure out all the files that need to be editted in order for gcc to output
> an instruction and understand how that instruction works. Currently I have
> it detecting the 'store' is an incorrect mnemoic (because I got define_inst
> outputting it). I would like to know if there are any recommended tutorials
> on how to add a instruction to the assembly language, and if there is an
> easier backend port that I should experiment on until I learn how to deal
> with all the components of RTL.

The machine description is responsible for generating the assembly text
(you'll see plenty of obvious examples of this).  Once the compiler is
emitting the right assembly source (compile with -S and inspect), then
you need to move onto the binutils to make the assembler recognise these
mnemonics.

What are you trying to do, exactly? :-)

Cheers, Ben

Re: Need help in a linking error

[Ben Elliston]

This list is for discussing GCC development, not deal with usage
problems.  Please try asking [EMAIL PROTECTED]

Thanks,
Ben

Re: Gcov: Coverage of Child processes

[Ben Elliston]

On Sun, 2008-09-28 at 10:03 +0530, J.P. Gupta wrote:

> I have a C++ server which in turn spawns the child process to do the
> execution of actual task. Using Gcov, I am getting the code coverage
> of the main server(listener) process but the child processes are not
> getting the coverage. Is it a known issue?  
> Do I need to make changes in my settings so that the Child processes
> get covered?

No, the gcov runtime is clever enough to deal with data being generated
by both the parent and child processes.  You should not need to do
anything special.

(follow-ups to gcc-help, please).

Cheers, Ben

Re: improving testsuite runtime

[Ben Elliston]

> Do people still use compare_tests?  Talking with Janis, she mentioned that
> it wasn't multilib (ie, RUNTESTFLAGS="--target_board=unix'{-m32,-m64}')
> compatible, but that test_summary was.  It's what I've been using to
> compare two runs.

I have used compare_tests for a long, long time.

Ben

PS: What's test_summary?  :-)

Re: improving testsuite runtime

[Ben Elliston]

> But stability within a given revision of the testsuite I think would be 
> almost essential.

Oh, of course :-)

Ben

Re: improving testsuite runtime

[Ben Elliston]

On Thu, 2008-09-18 at 10:44 -0600, Tom Tromey wrote:

> Ben> So, I guess my question is: what now?  What do people feel would be
> Ben> required to make this usable?  I assume that the most pressing thing
> Ben> would be to have the build system fold the various .log and .sum files
> Ben> together so that they look like they were run as a whole.

> Yeah, this seems necessary.  Ideally the order ought to be stable, too.

Do you think that the current order of .exps should be preserved in the
resultant .sum and .logs?  I guess some people and/or build farms
actually use diff rather than compare_tests?

Ben

improving testsuite runtime

[Ben Elliston]

While waiting on testsuites this week, I finally snapped and spent some
time looking at how to speed up the testsuite.

I did some experiments and collected data on the normalised runtimes of
each .exp test script.  I sorted them in descending order and these are
the top offenders:

 normalised  
dg.exp,gfortran 

  0.283 
execute.exp,gcc 

  0.142 
compile.exp,gcc 

  0.102 
execute.exp,gfortran 

  0.046 
struct-layout-1.exp,g++ 

  0.040 
struct-layout-1.exp,gcc 

  0.037 
dg.exp,g++ 

  0.037 
builtins.exp,gcc 

  0.036 






One problem with parallelising the gcc testsuite is that many of the
test drivers are not parallel safe.  So, rather than try to make them
all parallel safe, I decided we should just pick off the worst offenders
and manually schedule these (for all languages): run the big .exp
scripts in parallel with "the rest".  In the list above, for example,
gfortran and g++ dg.exp are run in parallel, despite belonging to
different languages.  For added robustness, each of the big test driver
is given its own testsuite directory (as we do now for checking
languages in parallel).

I ran as many of the top offenders in parallel as required to get "the
rest" to require the same normalised time as gfortran dg.exp, as we
cannot go any faster than the longest running .exp script.  I prototyped
this using the following shell script, which drives the make checks:

#!/bin/sh

# Run these in parallel:
tests="gfortran:dg.exp gcc:execute.exp gcc:compile.exp gfortran:execute.exp 
gcc:struct-layout-1.exp g++:struct-layout-1.exp g++:dg.exp gcc:builtins.exp 
gcc:dg.exp gcc:dg-torture.exp"

if [ ! -f auto-host.h ] ; then
  echo "not a gcc build directory"
  exit 1
fi

make testsuite/site.exp
for item in $tests ; do
make RUNTESTFLAGS="--tool ${item%:*} ${item#*:}" check-${item%:*} &
done

# Run the rest of the tests, but ignore the ones we've already run.
# Run all languages in parallel.
for tool in gcc g++ gfortran objc ; do
ignore=""
for item in $tests ; do
if [ ${item%:*} = ${tool} ] ; then
ignore="$ignore ${item#*:}"
fi
done
make RUNTESTFLAGS="--tool ${tool} --ignore $ignore" check-${tool} &
done
wait

Using this script and some minor gcc/Makefile.in hacks, I ran the entire
testsuite in 30% of the current time for a parallel-languages make
check.

So, I guess my question is: what now?  What do people feel would be
required to make this usable?  I assume that the most pressing thing
would be to have the build system fold the various .log and .sum files
together so that they look like they were run as a whole.

Another problem is that this is a bit of guesswork.  Maybe it would be
better to drive this from make -j, so that make takes care of the
scheduling (and we can push the longer tests to the front of the
dependency list, as we do to improve parallel builds now).

Comments?

Cheers, Ben

Re: Creating own Backend: Segmentation fault in mark_jump_label_1

[Ben Elliston]

> > The Error occures in mark_jump_label_1. It is called with a null pointer
> > as the rtx x.
> 
> Does nobody have an idea why or where the error occures? I really start
> to became desperate.

I'm sure plenty of people have an idea of why the error occurs.
However, you need to be clearer in explaining the problem so that people
have at least some hope of helping you, or doing so without consuming
excessive amounts of time from their schedules.

> I already changed a lot of Makros and analysed the the resulting gcc
> with gdb but I can't fix the error. I'm really grateful for every
> help!

Perhaps you could get a stack backtrace and try to understand why you're
getting a NULL_RTX passed in?

Ben

Re: gcc will become the best optimizing x86 compiler

[Ben Elliston]

> Since there is no libc mailing list, I thought that the gcc list is the 
> place to contact the maintainers of libc. Am I on the wrong list? Or are 
> there no maintainers of libc?

See:
  http://sources.redhat.com/glibc/

You want the libc-alpha list, I think.

Cheers, Ben

Re: GCC trunk frozen for the tuples merge

[Ben Elliston]

> The merge is done and the trunk is open again under the usual
> stage1 rules.

Don't forget to update svn.html. ;-)

Cheers, Ben

Re: machine cheat

[Ben Elliston]

OK, I give up.  What is the point of your messages and why is it the GCC
list that you've chosen to bother with them?

Ben

Re: C++ Warnings on trunk

[Ben Elliston]

> In this case, I argue that this code is always compiled with a C
> compiler, and should never be compiled by a C++ compiler.  Therefore,
> I believe it is wrong for this code to be compiled with the
> -Wc++-compat warning enabled.  This should be fixed somewhere in the
> configure script and/or Makefile.

I agree.  Aren't there some potential nasty problems here with the
shared libgcc being compiled with a C++ compiler and the ABI changing
one day?  (The C ABI, could, too, but it's much less likely.)

Ben

Re: handle preserving gcov

[Ben Elliston]

> Has anybody in the gcov developer community pondered  or done such a
> thing?

I have pondered it, yes.

Although it might not be a particularly helpful answer, have you
considered using other tools to get what you want rather than modify
gcov and the runtime code?  You could run the instrumented binary with
(say) one set of options, run gcov, gather the coverage output, and then
merge it into an "accumulated" report that includes what you want.
Repeat.

The main downside is that you have to run gcov over ever source file
after each binary invocation and then process the output.

Cheers, Ben

-- 
Ben Elliston <[EMAIL PROTECTED]>
Australia Development Lab, IBM

Re: [PATCH,rs6000] split up crtsavres into individual files

[Ben Elliston]

On Mon, 2008-06-23 at 15:52 -0700, Andrew Pinski wrote:

> http://gcc.gnu.org/ml/gcc-patches/2008-04/msg00324.html
> 
> This introduced a few warnings while building libgcc for powerpc64-linux-gnu:

I see lots and lots of these myself:

/home/bje/source/gcc-trunk/libgcc/shared-object.mk:26: warning: overriding 
commands for target `crtsavfpr.o'
/home/bje/source/gcc-trunk/libgcc/config/rs6000/t-ppccomm:109: warning: 
ignoring old commands for target `crtsavfpr.o'

Please fix! :-)

Thanks,
Ben

Re: Should we remove java from the default bootstrap languages?

[Ben Elliston]

On Sun, 2008-06-22 at 07:32 -0700, Ian Lance Taylor wrote:

> I think it would only be a few days of work for somebody familiar with
> Tcl to add -j support to DejaGNU.  I think that would be a very useful
> contribution to gcc development.

What did you have in mind, Ian?  That DejaGnu would run .exps in
parallel?  Perhaps what I tried is more complicated than what you are
proposing.

Cheers, Ben

Re: Should we remove java from the default bootstrap languages?

[Ben Elliston]

On Sun, 2008-06-22 at 19:13 +0200, Ralf Wildenhues wrote:

> Has anybody ever looked at using threading capabilities of tcl directly?
> Parallel DejaGNU could benefit other packages too.  There is a thread
> pools package (tpool.html, linked from ) but I
> have no idea how functional it is in practice; likely the GCC testsuite
> would need at least a bit of restructuring, too.

Yes, I tried it about 5 years ago.

I used Tcl safe interpreters to run each .exp script in isolation.  It
immediately raised some problems, namely that you have to decide what
variables and procs should be available to the interpreter.  This is
nice, in that it makes you decide what the public interface between
DejaGnu and a test script should be.  Its failing is that DejaGnu does
not have well-defined interfaces.  ;-)

In principle, it should work.  It was just a lot more work than I
bargained for.  Keep in mind that GCC does not have a huge number
of .exp scripts.  Some (eg. execute.exp) run many individual tests and,
if one wanted to, these scripts could be parallelised.  This just means
that there won't be wins for other scripts or other packages using
DejaGnu.

Ben

Re: Should we remove java from the default bootstrap languages?

[Ben Elliston]

On Sat, 2008-06-21 at 10:58 +0200, Ralf Wildenhues wrote:

> IIRC, then objects in libjava were built from lists of source files as a
> means to avoid per-object overhead of libtool and some other stuff, and
> to produce a bit better code[1].  Now, at least libtool compile mode
> overhead should be a fair bit lower than back then (upstream is a bit
> better, if that turns out to be significant, GCC could sync again).

A few years ago, I hacked the libjava Makefiles to eliminate the use of
libtool of Linux systems.  It cut 20 minutes from the build time on my
(at the time) modern hardware.

Ben

Re: Should we remove java from the default bootstrap languages?

[Ben Elliston]

On Fri, 2008-06-20 at 17:05 -0400, Diego Novillo wrote:

> On Fri, Jun 20, 2008 at 16:56, Kaveh R. GHAZI <[EMAIL PROTECTED]> wrote:
> 
> > That aside, our current policy already allows e.g. not testing java if
> > your change is to a part of the compiler that can't possible affect it.
> 
> I didn't make it completely clear, but my suggestion was mostly to
> help us middle/back-end hackers.

One practice I've started using is to use two build trees.  One I use in
my day-to-day work with only the C and C++ front-ends.  I have another
build tree that has all languages enabled that is built and tested
overnight (before I commit).  This means my changes get tested better,
but without me incurring the build delays.

Ben

Re: 4.4 deprecation proposals

[Ben Elliston]

On Sat, 2008-06-14 at 18:53 +, Joseph S. Myers wrote:

> m68k-*-aout*
> m68k-*-coff*

These would be fine with me; there has been no interest in these targets
in binutils-land for some time.

Ben

Re: How to post to GCC lists?

[Ben Elliston]

On Thu, 2008-05-22 at 15:09 -0500, Omar Torres wrote:

> 1- I noticed that when I reply to posts, the "References" are not
> preserved, which leads to messages in the same threat not to be linked
> together. I am using Thunderbird as my email client. When I go to
> View>Headers>All the References field looks accurate. Is there a trick
> to make this work? Should I use instead a different email client better
> suit for GCC ML?

I don't know what the problem is; Thunderbird should certainly observe
References: headers.  Whatever you do, please make sure it works.  We
have had list members use non-thread-aware mailers in the past and it's
certianly going to irritate people.

Welcome!

Ben

Re: Test Coverage not on whole execution (gcov)

[Ben Elliston]

On Wed, 2008-04-30 at 11:01 +0200, Fabien Baron wrote:

> I'm working on a big project in C code, and I want to profile it so I
> used gcc with the options -ftest-coverage and -fprofile-arcs, and gcov
> to analyze the results. It works very well but on the whole project
> and the whole execution !!
> My question is :
> Is it possible to start and stop profiling/coverage during the program
> execution ? If it is how I can do that ?

You should not need to compile every object file in the project with
those options.  Just compile the ones you want to generate coverage data
for (of course you will need those options to link).

By the way, you really should use --coverage to preserve your
sanity. ;-)

Cheers, Ben

Re: Question about compilation details

[Ben Elliston]

>I'm using the arm-elf-gcc compiler to compile some files to a ARM9
> (Freescale i.MX27, ARM926EJ-S core). What I would like to know is how
> can I visualize/change the address specifications made by the linker
> to the output file? I heard gcc can generate a file (.lst) that
> contains such information, but I also don't know how to create this
> file.

This question is probably better suited to gcc-help; this list is for
development discussions.  However, I will try and answer your question
nonetheless. ;-)

I assume you're referring to a linker map.  The GNU linker can create
one of these -- you need to refer to the ld man page for the details
(it's not really related to gcc).  To pass an option to the linker, pass
"-Wl," to gcc.

Cheers, Ben

-- 
Ben Elliston <[EMAIL PROTECTED]>
Australia Development Lab, IBM

Re: IRA for GCC 4.4

[Ben Elliston]

On Sun, 2008-04-27 at 21:45 +0200, J.C. Pizarro wrote:

> Don't be stupid!

Could you be a bit more civil, please?  It's fairly unusual for people
on this list to talk to each other in this way.

Thanks,
Ben

Re: RFC: named address space support

[Ben Elliston]

Hi Joseph

> > .. the embedded C proposal as of 2008-01-18 is at stage 90.92.  This
> > suggests that it's very close to being incorporated into the standard.
> > Have I understood that correctly?
> 
> No.  All it means is that TR 18037 is being revised, not anything to do 
> with the standard.  This is a TR Type 2, not an IS, and remains a TR Type 
> 2, not an IS.  [snip]

Thanks for the run-down on the standards process; very helpful!

> A TR Type 2 may be considered as indicating "if you want a feature to
> do this, it may be a good idea to do it this way and so gain
> implementation experience for future standardization".  As such, I
> think it is reasonable 
> to continue to add features from such TRs to GCC, provided we
> understand that they are experimental and may be changed incompatibly
> in future to accord with future TR versions or changes in the course
> of inclusion in the IS; that unlike actual language standards, we will
> not try to provide 
> options to support different versions of a TR in the same compiler
> version.  (The same applies to informative annexes in an IS, which may
> have the same sort of content as a Type 2 TR, such as Annex G in C99.)

This (in addition to Mark's comments) sounds perfectly acceptable to me.
We want the implementation to be standards compliant; if the standard
one day changes the details, we will have to change to be compliant.
Until then, the support should have a big neon sign over it that says
"experimental".

Cheers, Ben

Re: MAX_CONSTRAINT VALUE

[Ben Elliston]

Hi there Balaji,

>Here is the patch for it (if a value is not provided, then the
> default value of 30 is assumed). I tried to build this for x86 and arm
> and they seem to work fine with no problems.

Thanks for the patch.  You should send your patch to gcc-patches,
though, not the main GCC list.

Cheers, Ben

Re: RFC: named address space support

[Ben Elliston]

Hi Mark

> I'm not terribly familiar with this proposal.

> Ben, to answer your original question, I don't think that lack of nested 
> address spaces is a fatal flaw, as long as the implementation otherwise 
> meets the spec, and as long as the implementation doesn't somehow make 
> it harder to add that.  However, I'd like to know how final this 
> proposal is, and how likely it is to make the WG14 WP.

According to:
http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=30822

.. the embedded C proposal as of 2008-01-18 is at stage 90.92.  This
suggests that it's very close to being incorporated into the standard.
Have I understood that correctly?

> As always, I'm  concerned about putting things into GCC and then
> finding out that we have to change them in ways that are not backwards
> compatible.  And, I'd like to know what our C maintainers make of the
> proposal overall; if they see language issues, then we might want to
> resolve those with WG14.

Sure.  Any comments from Joseph or Richard?

Cheers, Ben

Re: RFC: named address space support

[Ben Elliston]

Hi Mark

> I agree.  Much to my dismay, the C and C++ committees don't seem to be 
> willing to work together to make sure that C remains a subset of C++. 

I'm afraid my patch doesn't address that.  :-)

> Ben, to answer your original question, I don't think that lack of nested 
> address spaces is a fatal flaw, as long as the implementation otherwise 
> meets the spec, and as long as the implementation doesn't somehow make 
> it harder to add that.

Good, I was hoping that would be the general opinion.

> However, I'd like to know how final this proposal is, and how likely
> it is to make the WG14 WP.

I don't really know the answer to that.  I will try and find out.
Perhaps Chao-ying Fu (cc'ed) who implemented the fixed point arithmetic
portion of the proposal knows more?

> As always, I'm concerned about putting things into GCC and
> then finding out that we have to change them in ways that are
> not backwards compatible.

Absolutely understood!

Cheers, Ben

Re: RFC: named address space support

[Ben Elliston]

> Is C++ supported?  I do know for that fixed point types, C++ is mostly
> supported (except mangling and a couple others). I think we should not
> be adding extension unless they are both supported in the C and C++
> front-ends.

C++ is not supported because this proposal came from WG14 (which is not
the C++ working group, WG21).  There is no such proposal from the C++
folks.

I don't know that implementing this right away in the C++ front-end is
such a great idea.  There will be plenty of proposals that come out of
the C working group that are perhaps not fully considered in the context
of C++.  There is so much potential for unanticipated interactions in C
++ that I think we should be very cautious about implementing C
extensions there just for completeness.

Cheers, Ben

RFC: named address space support

[Ben Elliston]

The Embedded-C spec introduces a number of C language features useful
for embedded development.  GCC already implements fixed point arithmetic
(Chapter 4) from this proposal.

  http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1169.pdf

Chapter 5 is divided into two sections: named address space support and
named-register storage classes.  IBM has an implementation of named
address space support on the named-addr-spaces-branch that we would like
to merge into mainline.  Before proceeding, I would like to discuss what
would be acceptable to the GCC community.

Our implementation only covers section 5.1 of the proposal (named
address space support).  Section 5.2 has not been implemented.

I am conscious that the named address space implementation we have is
not sufficiently generic to be acceptable for mainline and will need to
be cleaned up before being submitted.  In addition, there is no support
for nested address spaces and that is arguably a deficiency of any
implementation of this proposal.  Would this be acceptable, provided
that this limitation is documented?

Thanks, Ben

Re: instruction scheduling PowerPC target(s)

[Ben Elliston]

> Ideally I'd like to see the source code for the scheduler but I don't
> know where to find it. Can someone let me know where to get it,
> please?

See http://gcc.gnu.org/svn.html.  You can also look into the version
control system via a web interface, but that isn't well suited to
grep.  ;-)

Cheers, Ben

version control process improvement

[Ben Elliston]

I was speaking to Andrew Tridgell yesterday about how he uses svn with
the Samba project.  He mentioned an idea that we could pursue in the GCC
project.

As you know, Subversion keeps all branches and the trunk under different
paths in the repository.  Thus, it's possible to check out multiple
branches under a single directory tree.  eg:

  ~/source
gcc
  branches/gcc-4.2
  branches/gcc-4.3
  trunk

I don't know if anyone else does it this way; I don't.  By doing it this
way, it's possible to apply a patch to multiple branches and commit them
in a single changeset.  This has the advantage of allowing us to track
all of the branches a patch was committed to (at least initially;
someone may of course backport the patch at a later stage) with svn-log
-v.

Thoughts?

Cheers, Ben

Re: please add DFP to gcc-4.3/changes.html

[Ben Elliston]

Looks good to me.

Thanks,
Ben

Re: [linux-cirrus] Re: wot to do with the Maverick Crunch patches?

[Ben Elliston]

> The libm patch is for uClibc.

This thread is now off-topic for the GCC list.  Please take up the
discussion on a more appropriate list.

Thanks, Ben

Re: How should _Decimal64 and _Decimal128 be aligned on stack?

[Ben Elliston]

> DFP is beyond i386 psABI. Gcc aligns _Decimal32 to 4 byte, _Decimal64 to 8 
> bytes
> and _Decimal128 to 16bytes. The question is what is the best alignment for 
> them
> when passing to a functions.

The original work I did for the x86-64 backend placed them at that
alignment because that is the required alignment for loading those
values into SSE registers.  Right?

Ben

Re: MAINTAINERS update (was: [wwwdocs] java/projects.html -- remove broken link)

[Ben Elliston]

> Anyone knows how to update the following in MAINTAINERS?
> 
>   libgcj  Bryce McKinlay  [EMAIL PROTECTED]
> 
> The reason I am asking is that I just got
> 
>   <[EMAIL PROTECTED]>: host mx3.redhat.com[66.187.233.32] said:
>   550 5.2.1 <[EMAIL PROTECTED]>... Mailbox disabled for this recipient 
>   (in reply to RCPT TO command)

I believe that Bryce left Red Hat a while back.  Hopefully he's on the
java@ list and can speak up. :-)

> I'm wondering how many other entries in our MAINTAINERS file are affected.
> Perhaps we ought to send a test message to all and see what comes back?
> Thoughts?

I proposed something like this a while back.  I think we should do a
first pass, looking for domains that have vanished.  For the remainder,
send a ping message asking for a response.  Some employers have been
known to not bounce mail to an address, but forward it to someone else
in the company.  This makes it more difficult to ascertain of someone is
still working there.

Cheers, Ben

Re: Have proposals for 2008 gcc summit been reviewed?

[Ben Elliston]

> We submitted 2 proposals for 2008 gcc summit. We got one reply
> for one proposal on Mar. 15. But we haven't heard anything on
> the other. April 1 is the deadline for paper if proposal is
> accepted. Today is Mar. 20. I was wondering if anyone on
> gcc mailing list could help us figure out what happened to
> our other proposal.

All notifications should now have been sent out (I believe whether they
were accepted or not).

Cheers, Ben

Re: bootstrap failure on powerpc-linux

[Ben Elliston]

> The file was forgotten in the original commit it was fixed by the
> following revision:
> r133278 | paolo | 2008-03-16 11:35:44 -0700 (Sun, 16 Mar 2008) | 34 lines
> Changed paths:
>A /trunk/libstdc++-v3/include/std/date_time

I could have sworn my tree was sufficiently up to date.  Nonetheless, a
complete rebuild of my tree seems to have worked.  Thanks,

Ben

Re: An error occured when building gcc4.3.0

[Ben Elliston]

On Mon, 2008-03-17 at 18:09 +0800, [EMAIL PROTECTED] wrote:

> Hi I am new to this list. I try compiling gcc4.3.0 on mips machine
> with the follow command :

This list is for discussing the development of GCC, not building and
installing it.  Please direct your question to [EMAIL PROTECTED]
Thanks,

Ben

bootstrap failure on powerpc-linux

[Ben Elliston]

Anyone else seeing this?

libtool: compile:  /scratch/bje/bootstrap/./gcc/xgcc -shared-libgcc 
-B/scratch/bje/bootstrap/./gcc -nostdinc++ 
-L/scratch/bje/bootstrap/powerpc-linux/libstdc++-v3/src 
-L/scratch/bje/bootstrap/powerpc-linux/libstdc++-v3/src/.libs 
-B/usr/local/powerpc-linux/bin/ -B/usr/local/powerpc-linux/lib/ -isystem 
/usr/local/powerpc-linux/include -isystem /usr/local/powerpc-linux/sys-include 
-I/scratch/bje/bootstrap/powerpc-linux/libstdc++-v3/include/powerpc-linux 
-I/scratch/bje/bootstrap/powerpc-linux/libstdc++-v3/include 
-I/home/bje/source/gcc-trunk/libstdc++-v3/libsupc++ -fno-implicit-templates 
-Wall -Wextra -Wwrite-strings -Wcast-qual -fdiagnostics-show-location=once 
-ffunction-sections -fdata-sections -g -O2 -D_GNU_SOURCE -std=gnu++0x -c 
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc  -fPIC -DPIC -o 
.libs/date_time.o
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:28:21: error: 
date_time: No such file or directory
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:32: error: 
'system_time' does not name a type
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:39: error: 
'nanoseconds' has not been declared
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:39: error: expected 
initializer before 'nanoseconds'
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:40: error: 
'nanoseconds' has not been declared
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:40: error: expected 
initializer before 'nanoseconds'
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:41: error: 
'nanoseconds' has not been declared
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:41: error: 
uninitialized const 'std::is_subsecond'
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:43: error: 
'system_time' has not been declared
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:43: error: expected 
initializer before 'system_time'
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:44: error: 
'system_time' has not been declared
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:44: error: expected 
initializer before 'system_time'
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:45: error: 
'system_time' has not been declared
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:45: error: 
redefinition of 'const bool std::is_subsecond'
/home/bje/source/gcc-trunk/libstdc++-v3/src/date_time.cc:41: error: 'const bool 
std::is_subsecond' previously declared here

Ben

Re: Official GCC git repository

[Ben Elliston]

> David Woodhouse wrote:

> > To be honest, I find it weird that Subversion even exists. Precisely
> > because it _is_ so close to what people were using before, as you point
> > out. I've never really understood why anyone would bother to change from
> > CVS to SVN -- it just seems to be part of the 'one VCS per project'
> > insanity.

I remember seeing a talk by Jim Blandy on Subversion around 2001.  At
the time, the CVS-using community in the audience were (vocally)
impressed by what a huge step forward it was in addressing the
limitations of CVS.

There are indeed other choices out there these days, but at the time it
began, Subversion made a lot of sense.

Ben

Re: RTL definition

[Ben Elliston]

> I thought that RTL represented something close to the target machine,
> but not machine-dependent. I firstly thought that the output of the
> middle-end was an RTL machine-independent representation, to which is
> applied a few low-optimization machine-independent passes, and after
> that is translated to a RTL machine-dependent to be applied other
> optimization passes.

There are certain details that you will discover in the RTL that makes
it highly machine-dependent.  For example, the register number where
functions place their values is defined by the ABI and implemented by
the backend.  RTL is by no means machine neutral.

Cheers, Ben

-- 
Ben Elliston <[EMAIL PROTECTED]>
Australia Development Lab, IBM

Re: Porting gcc

[Ben Elliston]

On Wed, 2008-03-12 at 16:56 +1100, Schmave wrote:
> Hi I would luke to know what I need to do to port gcc to a new  
> architecture

You can start by reading the GCC internals documentation:

  http://gcc.gnu.org/onlinedocs/gccint/

You can also look at the source code, in particular, the gcc/config
directory.

Finally, you have the option of hiring someone to do the port for you:

  http://www.fsf.org/resources/service

Cheers, Ben

Re: howto run cross testings with help of translators

[Ben Elliston]

> I have a developing cross compiler sparc-sun-solaris2.10-gcc on x86.
> There is an available binary translator that could execute SPARC ELF
> on x86 machines. so I want to run testings by runtest. It would
> definitely help a lot if anyone could give clues on how to manage it.

You want a SPARC simulator that can run under DejaGnu.  If you can find
a setup that would allow you to run "sparcsim ", that would be
best, as it would make the DejaGnu setup quite simple -- see the other
Dejagnu baseboard files for examples.

Another way is to find a full system simulator, boot an operating system
with a telnet/ftp server running and have DejaGnu copy the test cases
into the simulator and then log in to execute them.  In that case, the
setup is more like a convention cross-testing arrangement where the
machine doing the testing logs into the target.

Anyway, this is probably off-topic for the GCC list.  Please direct any
follow-ups to the DejaGnu mailing list.  Thanks.

Ben