Re: Is "FTZ/DAZ for SSE via fast math" available for x86 arch other than Linux?
Hello! Maybe such optimization isn't turned on for mingw. I updated the patch to force this by using -minline-all-stringops. http://gcc.gnu.org/bugzilla/attachment.cgi?id=13189 Any developer to have a look at this? Please post the patch to [EMAIL PROTECTED] Also add appropriate ChangeLog and a reference to the PR. I can find the patch, but can't find the PR from your message. Patch contribution procedure is described in great detail at http://gcc.gnu.org/contribute.html. Thanks, Uros.
Re: Is "FTZ/DAZ for SSE via fast math" available for x86 arch other than Linux?
Hi, 2007/5/21, Uros Bizjak <[EMAIL PROTECTED]>: Hello! >> Maybe such optimization isn't turned on for mingw. I updated the patch >> to force this by using -minline-all-stringops. >> >> http://gcc.gnu.org/bugzilla/attachment.cgi?id=13189 > > Any developer to have a look at this? Please post the patch to [EMAIL PROTECTED] Also add appropriate ChangeLog and a reference to the PR. I can find the patch, but can't find the PR from your message. It's PR 29498. Thanks! Patch contribution procedure is described in great detail at http://gcc.gnu.org/contribute.html. -- Zuxy Beauty is truth, While truth is beauty. PGP KeyID: E8555ED6
Re: A reload inheritance bug
On Tue, May 15, 2007 at 04:27:21PM +0100, Mark Shinwell wrote: > Part of the reason for starting this thread was that I was concerned > about invalidating reloads that could be re-used later. However, it > seems to me that in every circumstance where the reload register is a > hard register and the value assigned to that reload register is > different from the value held by the register during the evaluation of > the subexpression being reloaded (as we have here with r9 <- r9 + r10), > we must invalidate all previous reloads involving that hard register. > I may well have encoded that logic incorrectly in the patch, though. I'd say try the usual testing procedure with the addition of saving away libgcc, newlib, libiberty etc. for code size comparison. If you find any, at least we'll be that much wiser. -- Rask Ingemann Lambertsen
Basic block execution records in gprof
Hello all, According to GNU gprof manual http://www.gnu.org/software/binutils/manual/gprof-2.9.1/html_chapter/gprof_5.html#SEC18 basic-block counting can be analyzed with gprof if a program is augmented for that.For this the program is to be compiled with `gcc ... -g -pg -a' option . But '-a' option has been replaced with -fprofile-arcs and with this options the output files are actually produced for gcov. But GNU C library has code for printing basic block records on to gmon.out file. So is it possible to do the above with gprof ? If it is possible with is the option that has to be used when compiling the program? Thanks for your time. Regards, Shafi
a question regarding ifcvt.c
Hi, I'd like to get an explanation why ifcvt.c checks whether 1 of the 2 successors of the IF-header block has a stmt that exits from the loop? Why does it prevent the if-conversion? I'm referring to the following code: /* Nor exit the loop. */ if ((then_edge->flags & EDGE_LOOP_EXIT) || (else_edge->flags & EDGE_LOOP_EXIT)) return NULL; Thanks, Tehila.
A question about push_reload()
I think push_reload() is doing something weird with this insn:
Breakpoint 1, find_reloads (insn=0xb7f7e348, replace=0, ind_levels=0,
live_known=0, reload_reg_p=0x8878a7c) at ../../../cvssrc/gcc/gcc/reload.c:2535
2535{
(gdb) call debug_rtx(insn)
(insn 12 10 16 2 /tmp/ashiftsi3_1.c:3 (parallel [
(set (subreg:HI (reg:SI 2 a [orig:20 D.1497 ] [20]) 0)
(ashift:HI (reg:HI 8 si [orig:26 x ] [26])
(const_int 1 [0x1])))
(clobber (reg:CC 13 cc))
]) 353 {*ashlhi3} (nil)
(expr_list:REG_DEAD (reg:HI 8 si [orig:26 x ] [26])
(expr_list:REG_UNUSED (reg:CC 13 cc)
(insn_list:REG_RETVAL 13 (nil)
where operands 0 and 1 must match. The resulting reloads are:
Spilling for insn 12.
Using reg 8 for reload 0
Reloads for insn # 12
Reload order: 0
Reload 0: reload_in (HI) = (reg:HI 26 [ x ])
reload_out (SI) = (reg:SI 2 a [orig:20 D.1497 ] [20])
GENERAL_REGS, RELOAD_OTHER (opnum = 0)
reload_in_reg: (reg:HI 26 [ x ])
reload_out_reg: (reg:SI 2 a [orig:20 D.1497 ] [20])
reload_reg_rtx: (reg:SI 8 si)
;; Register dispositions:
20 in 2 21 in 8 22 in 9 23 in 2 24 in 0 25 in 0
It seems unnecessary to create a SImode output reload here and worse, it
clobbers (reg:HI 4 d) which is live ((reg:SI 2 a) is four registers):
(insn 40 10 12 2 /tmp/ashiftsi3_1.c:3 (set (reg:HI 8 si)
(mem/c:HI (plus:HI (reg/f:HI 10 bp)
(const_int -2 [0xfffe])) [0 S2 A8])) 9 {*movhi} (nil)
(nil))
(insn 12 40 41 2 /tmp/ashiftsi3_1.c:3 (parallel [
(set (reg:HI 8 si)
(ashift:HI (reg:HI 8 si)
(const_int 1 [0x1])))
(clobber (reg:CC 13 cc))
]) 353 {*ashlhi3} (nil)
(nil))
(insn 41 12 42 2 /tmp/ashiftsi3_1.c:3 (set (reg:HI 2 a [orig:20 D.1497 ] [20])
(reg:HI 8 si)) 9 {*movhi} (nil)
(nil))
(insn 42 41 14 2 /tmp/ashiftsi3_1.c:3 (set (reg:HI 4 d [ D.1497+2 ])
(reg:HI 9 di [+2 ])) 9 {*movhi} (nil)
(nil))
Register di was dead at this point, btw. The call to push_reload() seems
OK:
push_reload (in=0xb7f833b0, out=0xb7f7578c, inloc=0xb7f758bc,
outloc=0xb7f758c8, class=GENERAL_REGS, inmode=HImode, outmode=HImode,
strict_low=0, optional=0,
opnum=0, type=RELOAD_OTHER) at ../../../cvssrc/gcc/gcc/reload.c:929
(gdb) call debug_rtx(in)
(reg:HI 8 si [orig:26 x ] [26])
(gdb) call debug_rtx(out)
(subreg:HI (reg:SI 2 a [orig:20 D.1497 ] [20]) 0)
Starting at line 1097 of reload.c is the interesting part:
/* Similarly for paradoxical and problematical SUBREGs on the output.
Note that there is no reason we need worry about the previous value
of SUBREG_REG (out); even if wider than out,
storing in a subreg is entitled to clobber it all
(except in the case of STRICT_LOW_PART,
and in that case the constraint should label it input-output.) */
[...]
|| (REG_P (SUBREG_REG (out))
&& REGNO (SUBREG_REG (out)) < FIRST_PSEUDO_REGISTER
&& ((GET_MODE_SIZE (outmode) <= UNITS_PER_WORD
&& (GET_MODE_SIZE (GET_MODE (SUBREG_REG (out)))
> UNITS_PER_WORD)
&& ((GET_MODE_SIZE (GET_MODE (SUBREG_REG (out)))
/ UNITS_PER_WORD)
!= (int) hard_regno_nregs[REGNO (SUBREG_REG (out))]
[GET_MODE (SUBREG_REG (out))]))
|| ! HARD_REGNO_MODE_OK (subreg_regno (out), outmode)))
[...]
{
out_subreg_loc = outloc;
outloc = &SUBREG_REG (out);
out = *outloc;
#if ! defined (LOAD_EXTEND_OP) && ! defined (WORD_REGISTER_OPERATIONS)
gcc_assert (!MEM_P (out)
|| GET_MODE_SIZE (GET_MODE (out))
<= GET_MODE_SIZE (outmode));
#endif
outmode = GET_MODE (out);
}
What is the condition with hard_regno_nregs[][] supposed to check?
In this particular case, we have:
GET_MODE_SIZE (GET_MODE (SUBREG_REG (out))) = 4
UNITS_PER_WORD = 2
hard_regno_nregs[2][SImode] = 4 (8-bit registers)
so the condition 4 / 2 != 4 is true and reload thinks the SUBREG is
problematical. I don't see what is problematical about it.
I tried to "svn blame" someone, but ended with:
r363 | kenner | 1992-02-28 11:23:25 +0100 (fre, 28 feb 1992) | 2 lines
Initial revision
--
Rask Ingemann Lambertsen
Problem when using optimization on aix 5.2 and gcc 4.1.1
Hello, We have a large app with a lot of static libraries in it (and I mean a lot, about 20) and it compiles and links successfully. If I compile it without optimiztion turned on (-O2 or some more subtle with -O and others), the program also runs. With optimizations, though, the program would crash. Entailed is the gdb stacktrace. We use the native linker of aix and are updated to the latest bos packages for 5.2. Thanks for hints! thomas Eventc, which has no line number information. 0xd12c04b0 in XtDispatchEventToWidget () from /usr/lib/libXt.a(shr4.o) (gdb) c Continuing. terminate called after throwing an instance of 'std::bad_cast' what(): St8bad_cast Program received signal SIGABRT, Aborted. 0xd005b288 in pthread_kill () from /usr/lib/libpthreads.a(shr_xpg5.o) (gdb) bt #0 0xd005b288 in pthread_kill () from /usr/lib/libpthreads.a(shr_xpg5.o) #1 0xd005ad24 in _p_raise () from /usr/lib/libpthreads.a(shr_xpg5.o) #2 0xd01f20a4 in raise () from /usr/lib/libc.a(shr.o) #3 0xd0212758 in abort () from /usr/lib/libc.a(shr.o) #4 0xd287e6f0 in __gnu_cxx::__verbose_terminate_handler () at _start_ :97 #5 0xd2886cb8 in __cxxabiv1::__terminate (handler=) at _start_ :43 #6 0xd287e57c in std::terminate () at _start_ :53 #7 0xd2886ae8 in __cxa_throw (obj=, tinfo=, dest=) at _start_ :77 #8 0xd2894714 in std::__throw_bad_cast () at _start_ :55 #9 0xd28d31ec in std::basic_ios >::widen ( this=, __c=10 '\n') from /opt/compiler/gcc-4.1/bin/../lib/gcc/powerpc-ibm-aix5.2.0.0/4.1.1/libstdc++.a(libstdc++.so.6) #10 0x118ffd38 in ReadLine () #11 0x11901e00 in ReadStlFile () #12 0x103488d4 in FEMeshPartC::ReadSTL () #13 0x10b03a68 in AssPoolItemNativeC::LoadPart () #14 0x10afd1b4 in AssRefItemNativeC::TableChanged () #15 0x10b111f0 in AssFactoryNativeC::SelectDefaultLines () #16 0x10b0febc in AssFactoryNativeC::BuildRefAssItem () [EMAIL PROTECTED] gcc -v Using built-in specs. Target: powerpc-ibm-aix5.2.0.0 Configured with: ../gcc-4.1.1/configure --enable-version-specific-runtime-libs --enable-languages=c,c++ --enable-static --enable-shared --enable-threads --prefix=/opt/gcc-4.1 --without-gnu-ld --disable-nls --with-pic --disable-symvers --enable-symvers=no Thread model: aix gcc version 4.1.1
Re: Problem when using optimization on aix 5.2 and gcc 4.1.1
On Mon, May 21, 2007 at 07:06:47PM +0200, Thomas Mittelstaedt wrote: > Hello, > > We have a large app with a lot of static libraries in it (and I mean a > lot, about 20) and it compiles and links successfully. If I compile it > without optimiztion turned on > (-O2 or some more subtle with -O and others), the program also runs. > With optimizations, though, the program would crash. While compiler bugs are possible, it is much more likely that it is a program bug. Common causes are uninitialized memory or heap corruption; the effects of this tend to change with optimization.
Re: I don't understand some of gcc-4.1-20070514, a patch here.
On May 19, 2007, at 11:54 AM, Manuel López-Ibáñez wrote: We tried to be polite And we should go back to being polite... He's email a patch recently. That's buys him more niceness in my book. I think he does want to help, he just needs more guidance. Our goal is to turn him into a useful contributor. Now, to get him to download 4.3 and fix it instead of 4.1. :-)
Re: I don't understand some of gcc-4.1-20070514, a patch here.
On May 19, 2007, at 3:57 AM, J.C. Pizarro wrote: you have this nice cleanup's patch of gcc/loop.c that transliterates the logic of the uses of the loop_invariant_p (..) and consec_sets_invariant_p (..) functions. Please resubmit against 4.3 (the top of the svn tree)... This is the canonical place where developers should be doing development. Thanks.
Re: I don't understand some of gcc-4.1-20070514, a patch here.
On 5/21/07, Mike Stump <[EMAIL PROTECTED]> wrote: Please resubmit against 4.3 (the top of the svn tree)... This is the canonical place where developers should be doing development. Thanks. Except loop.c has been removed already which has mentioned like 5 time already. Thanks, Andrew Pinski
Re: I don't understand some of gcc-4.1-20070514, a patch here.
On Mon, May 21, 2007 at 11:00:17AM -0700, Mike Stump wrote: > On May 19, 2007, at 3:57 AM, J.C. Pizarro wrote: > >you have this nice cleanup's patch of gcc/loop.c that > >transliterates the logic > > of the uses of the loop_invariant_p (..) and > >consec_sets_invariant_p (..) > > functions. > > Please resubmit against 4.3 (the top of the svn tree)... This is the > canonical place where developers should be doing development. Thanks. But gcc/loop.c is only in 4.1.x. It is not in 4.2.0, and not in the trunk. The patch can't be re-submitted against the trunk.
Re: a question regarding ifcvt.c
Tehila Meyzels <[EMAIL PROTECTED]> writes: > I'd like to get an explanation why ifcvt.c checks whether 1 of the 2 > successors of the IF-header block has a stmt that exits from the loop? > Why does it prevent the if-conversion? > I'm referring to the following code: > > /* Nor exit the loop. */ > if ((then_edge->flags & EDGE_LOOP_EXIT) > || (else_edge->flags & EDGE_LOOP_EXIT)) > return NULL; I think it's just a heuristic. If one of the edges exits the loop, then it is probably a loop-exit test, and it is quite unlikely that we can do any useful if-conversion. Ian
Re: 4.3 release plan
Brooks Moses wrote: >> What about moving 4.3 to stage 3 *now* and moving everything >> else in 4.4 instead? Hopefully, it will be a matter of just >> a few months. From http://gcc.gnu.org/gcc-4.3/changes.html, >> it looks like it would already be quite a juicy release. > > Why? > > I mean, I suppose there could be advantages to doing this, but you > haven't mentioned even one. I apologize. I guess you could get 10 different reasons by 10 different people. The reason _we_ care to get 4.3 sooner rather than later is that we'd like to have the AMD Geode tuning and the memcpy/strcpy() optimizations. And also: why not? -- // Bernardo Innocenti \X/ http://www.codewiz.org/
Re: 4.3 release plan
On 5/21/07, Bernardo Innocenti <[EMAIL PROTECTED]> wrote: And also: why not? I had hoped to get my pointer plus branch merged in which should improve code gen and memory usage and compile time. -- Pinski
Re: 4.3 release plan
On Mon, May 21, 2007 at 11:31:19AM -0700, Andrew Pinski wrote: > On 5/21/07, Bernardo Innocenti <[EMAIL PROTECTED]> wrote: > >And also: why not? > > I had hoped to get my pointer plus branch merged in which should > improve code gen and memory usage and compile time. There seem to be quite a large number of not-yet-merged projects on the wiki page at http://gcc.gnu.org/wiki/GCC_4.3_Release_Planning "Go straight to phase 3" would presumably mean that none of them get in. On the other hand, phase 1 has been running for a long time, long past its original end date. I'm surprised that phase 2 hasn't started.
Re: 4.3 release plan
On May 21, 2007, at 11:23 AM, Bernardo Innocenti wrote: The reason _we_ care to get 4.3 sooner rather than later is that we'd like to have the AMD Geode tuning Submit to gcc 4.2. Tuning seems to be the type of thing that should be safe to backport, if you really must have it. Anyway, these reasons don't sound like reasons to goose the 4.3 plan. I'd argue for status quo.
Re: a question regarding ifcvt.c
On 5/21/07, Tehila Meyzels <[EMAIL PROTECTED]> wrote: Hi, I'd like to get an explanation why ifcvt.c checks whether 1 of the 2 successors of the IF-header block has a stmt that exits from the loop? Why does it prevent the if-conversion? I'm referring to the following code: /* Nor exit the loop. */ if ((then_edge->flags & EDGE_LOOP_EXIT) || (else_edge->flags & EDGE_LOOP_EXIT)) return NULL; To prevent ifcvt from moving computations into loops. See this patch: http://gcc.gnu.org/ml/gcc-patches/2003-07/msg01864.html Gr. Steven
Re: I don't understand some of gcc-4.1-20070514, a patch here.
On 5/21/07, Andrew Pinski <[EMAIL PROTECTED]> wrote: On 5/21/07, Mike Stump <[EMAIL PROTECTED]> wrote: > Please resubmit against 4.3 (the top of the svn tree)... This is the > canonical place where developers should be doing development. Thanks. Except loop.c has been removed already which has mentioned like 5 time already. Let's make a guess: Mike still sees loop.c in GCC 4.2 *His* GCC 4.2 tree that is (Apple's) Just like the last minute GCC 4.2 bug that wasn't an FSF GCC 4.2 bug ;-) Joke joke... Gr. Steven
Re: 4.3 release plan
Joe Buck wrote: >> I had hoped to get my pointer plus branch merged in which should >> improve code gen and memory usage and compile time. > > There seem to be quite a large number of not-yet-merged projects > on the wiki page at Never mind, I just did some investigation and it appears that the patches we want are quite trivial to backport to 4.2, so we don't need to rush 4.3 out. > "Go straight to phase 3" would presumably mean that none of them get > in. But on the other end, if we do push GCC 4.3 out now, there will be another stage 1 very soon :-) Well, I don't want to step on anybody's feet. GCC has historically had longer release cycles than other projects of comparable size and this has clearly been consciously planned by experienced people, most probably for good reason. For the impatient, backporting is always an option. -- // Bernardo Innocenti \X/ http://www.codewiz.org/
Re: I don't understand some of gcc-4.1-20070514, a patch here.
2007/5/21, Mike Stump <[EMAIL PROTECTED]> wrote: On May 19, 2007, at 3:57 AM, J.C. Pizarro wrote: > you have this nice cleanup's patch of gcc/loop.c that > transliterates the logic > of the uses of the loop_invariant_p (..) and > consec_sets_invariant_p (..) > functions. Please resubmit against 4.3 (the top of the svn tree)... This is the canonical place where developers should be doing development. Thanks. It's impossible to resubmit the similar patch to >=4.2. Try this command $ grep -iR loop_invariant_p . | grep '\.c:\|\.h:' $ So, you can compare the lectures of loop invariant's algorithms between 4.1.3-ss, 4.2 and 4.3. The main difference is that patched 4.1.3-ss works well, it's 3in1 in the loop function and is comprehensible. Since 4.2, it'd changed a lot! it's 2in1! I hate the '-b-r-a-i-n-f-u-c-k-e-d- -c-o-d-e- -w-i-t-h-o-u-t- -e-x-p-l-a-n-a-t-i-o-n-'.
help writing gcc code
I need to edit a gcc source code, then recompile. My goal is to change what gets output in the assembly file, when using the '-S' flag. I figured a good first step would be, being able to print out "Hello World!" somewhere in the '.s' file. I'm having trouble finding which source code file I need to edit though. Any help would be great. Thanks. -- View this message in context: http://www.nabble.com/help-writing-gcc-code-tf3793037.html#a10727717 Sent from the gcc - Dev mailing list archive at Nabble.com.
Re: help writing gcc code
On May 21, 2007, at 2:43 PM, AaronCloyd wrote: I need to edit a gcc source code, then recompile. Wrong list... gcc-help is closer that what you want...
Re: I don't understand some of gcc-4.1-20070514, a patch here.
2007/5/21, Mike Stump <[EMAIL PROTECTED]> wrote:
On May 21, 2007, at 2:04 PM, J.C. Pizarro wrote:
> I hate the '-b-r-a-i-n [ ... ]
We don't use that sort of language around here...
Don't you understand the b-r-a-i-n-f-u-c-k-e-d source code?
http://en.wikipedia.org/wiki/Brainfuck
I'm saying is that you do not develop the source code directly to machine
and distantly to the human natural language.
The lecture of the legible source code is more important than brainfucking
the source code for maximum speed.
I hate "if (ptr) { ... }" /* <- It's b-r-a-i-n-f-u-c-k-e-d source code! */
I love "if (ptr != NULL) { ... }"
Re: Problem when using optimization on aix 5.2 and gcc 4.1.1
Thomas Mittelstaedt wrote: Hello, We have a large app with a lot of static libraries in it (and I mean a lot, about 20) and it compiles and links successfully. If I compile it without optimiztion turned on (-O2 or some more subtle with -O and others), the program also runs. With optimizations, though, the program would crash. Entailed is the gdb stacktrace. We use the native linker of aix and are updated to the latest bos packages for 5.2. You need to debug the program to find out where the bug is (most likely the bug is in your code, optimization often shows up bugs that do not appear at -O0).
Volunteer for bug summaries?
I've received some feedback suggesting that some contributors may not always be aware of what open issues are available to work on, and, perhaps more importantly, what regressions they may have caused. Is there a volunteer who would like to help prepare a regular list of P3-and-higher PRs, together with -- where known -- the name of the person responsible for the checkin which caused the regression? Or, is this something that could be automated through Bugzilla, perhaps by adding a pointer to the SVN revision at which the regression was introduced? The goal would be to send a weekly/bi-weekly reminder to the list, and to the responsible parties, to help remind those of us who've caused problems to clean them up. I know that this would help me, both as a developer and as the RM: as RM, it would help me see what's going on, and as a developer, it would encourage me to clean up my messes, even when I'm busy. What do others think? Thanks, -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713
Re: Volunteer for bug summaries?
On Mon, May 21, 2007 at 03:35:53PM -0700, Mark Mitchell wrote: > Is there a volunteer who would like to help prepare a regular list of > P3-and-higher PRs, together with -- where known -- the name of the > person responsible for the checkin which caused the regression? Or, is > this something that could be automated through Bugzilla, perhaps by > adding a pointer to the SVN revision at which the regression was introduced? A semi-automated approach would be to add a field in Bugzilla that would contain the SVN revision; this field could be filled in by volunteers, and then a Bugzilla query could generate the report whenever you want to look at it. Of course, some bugs predate the conversion to Bugzilla, and release branches complicate life a bit.
gcc-4.1-20070521 is now available
Snapshot gcc-4.1-20070521 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20070521/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.1 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_1-branch revision 124925 You'll find: gcc-4.1-20070521.tar.bz2 Complete GCC (includes all of below) gcc-core-4.1-20070521.tar.bz2 C front end and core compiler gcc-ada-4.1-20070521.tar.bz2 Ada front end and runtime gcc-fortran-4.1-20070521.tar.bz2 Fortran front end and runtime gcc-g++-4.1-20070521.tar.bz2 C++ front end and runtime gcc-java-4.1-20070521.tar.bz2 Java front end and runtime gcc-objc-4.1-20070521.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.1-20070521.tar.bz2The GCC testsuite Diffs from 4.1-20070514 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.1 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: 4.3 release plan
Mike Stump wrote: > Submit to gcc 4.2. Tuning seems to be the type of thing that should > be safe to backport, if you really must have it. I extracted the relevant patches that would apply to 4.2 as they were. Currently regtesting just in case. -- // Bernardo Innocenti \X/ http://www.codewiz.org/
Re: 4.3 release plan
Bernardo Innocenti wrote: > I extracted the relevant patches that would apply > to 4.2 as they were. Currently regtesting just in > case. Err, allow me to rephrase that more clearly: I have extracted the Geode patches from the trunk and they applied without modification to the 4.2 branch. I'm currently bootstrapping 4.2 with "--with-arch=geode" and will run the testsuite shortly. -- // Bernardo Innocenti \X/ http://www.codewiz.org/
Re: Volunteer for bug summaries?
is is very difficult work? i did't know whether i can competent for it. i'.m a volunteer. On 5/22/07, Mark Mitchell <[EMAIL PROTECTED]> wrote: I've received some feedback suggesting that some contributors may not always be aware of what open issues are available to work on, and, perhaps more importantly, what regressions they may have caused. Is there a volunteer who would like to help prepare a regular list of P3-and-higher PRs, together with -- where known -- the name of the person responsible for the checkin which caused the regression? Or, is this something that could be automated through Bugzilla, perhaps by adding a pointer to the SVN revision at which the regression was introduced? The goal would be to send a weekly/bi-weekly reminder to the list, and to the responsible parties, to help remind those of us who've caused problems to clean them up. I know that this would help me, both as a developer and as the RM: as RM, it would help me see what's going on, and as a developer, it would encourage me to clean up my messes, even when I'm busy. What do others think? Thanks, -- Mark Mitchell CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713 -- i'm a newbie in GCC community. Wei Chen
GCC, Wei Chen wants to chat
I've been using Google Talk and thought you might like to try it out. We can use it to call each other for free over the internet. Here's an invitation to download Google Talk. Give it a try! --- Wei Chen wants to stay in better touch using some of Google's coolest new products. If you already have Gmail or Google Talk, visit: http://mail.google.com/mail/b-2e449a07c2-e08b71486f-e1969e1dac77466f You'll need to click this link to be able to chat with Wei Chen. To get Gmail - a free email account from Google with over 2,800 megabytes of storage - and chat with Wei Chen, visit: http://mail.google.com/mail/a-2e449a07c2-e08b71486f-10549a4ddb Gmail offers: - Instant messaging right inside Gmail - Powerful spam protection - Built-in search for finding your messages and a helpful way of organizing emails into "conversations" - No pop-up ads or untargeted banners - just text ads and related information that are relevant to the content of your messages All this, and its yours for free. But wait, there's more! By opening a Gmail account, you also get access to Google Talk, Google's instant messaging service: http://www.google.com/talk/ Google Talk offers: - Web-based chat that you can use anywhere, without a download - A contact list that's synchronized with your Gmail account - Free, high quality PC-to-PC voice calls when you download the Google Talk client Gmail and Google Talk are still in beta. We're working hard to add new features and make improvements, so we might also ask for your comments and suggestions periodically. We appreciate your help in making our products even better! Thanks, The Google Team To learn more about Gmail and Google Talk, visit: http://mail.google.com/mail/help/about.html http://www.google.com/talk/about.html (If clicking the URLs in this message does not work, copy and paste them into the address bar of your browser).
Re: GCC, Wei Chen wants to chat
On 5/21/07, Wei Chen <[EMAIL PROTECTED]> wrote: I've been using Google Talk and thought you might like to try it out. I would suggest that you use the public IRC channel on irc.oftc.net. See the GCC wiki page for details (http://gcc.gnu.org/wiki/GCConIRC)
Re: help writing gcc code
Mike Stump wrote: On May 21, 2007, at 2:43 PM, AaronCloyd wrote: I need to edit a gcc source code, then recompile. Wrong list... gcc-help is closer that what you want... Is it? Changing the internals of what GCC puts into .s files seems a topic that's more appropriate here, I would think. - Brooks
Re: help writing gcc code
i think you can read GCC backend to understand GCC how to write .s files. On 5/22/07, Brooks Moses <[EMAIL PROTECTED]> wrote: Mike Stump wrote: > On May 21, 2007, at 2:43 PM, AaronCloyd wrote: >> I need to edit a gcc source code, then recompile. > > Wrong list... gcc-help is closer that what you want... Is it? Changing the internals of what GCC puts into .s files seems a topic that's more appropriate here, I would think. - Brooks -- i'm a newbie in GCC community. Wei Chen
http://gcc.gnu.org/svn.html have a error.
i think http://gcc.gnu.org/svn.html have a error. "Using the SVN repository Assuming you have version 1.0.0 and higher of Subversion installed, you can check out the GCC sources using the following command: svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc " the right is svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk orsvn -q checkout svn://gcc.gnu.org/svn/gcc/trunk/gcc -- i'm a newbie in GCC community. Wei Chen
Re: http://gcc.gnu.org/svn.html have a error.
On 5/21/07, Wei Chen <[EMAIL PROTECTED]> wrote: svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc " the right is svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk Not really, the syntax mentioned in the page is correct. The additional argument 'gcc' merely means that on checkout, 'trunk' will be created as 'gcc' in your local copy. orsvn -q checkout svn://gcc.gnu.org/svn/gcc/trunk/gcc Careful with this one. If you use this syntax, you will only be checking out the trunk/gcc sub-directory and will not be able to build the compiler.
Re: http://gcc.gnu.org/svn.html have a error.
Wei Chen wrote: i think http://gcc.gnu.org/svn.html have a error. "Using the SVN repository Assuming you have version 1.0.0 and higher of Subversion installed, you can check out the GCC sources using the following command: svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc " I think you are mistaken. The command above does in fact check out the source into a directory named gcc. the right is svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk This will work as well, but the workspace will be in a directory called 'trunk' orsvn -q checkout svn://gcc.gnu.org/svn/gcc/trunk/gcc That is probably not what you want. That will only checkout the gcc subdirectory. The result while interesting, will not be sufficient to build a working compiler. David Daney
Re: http://gcc.gnu.org/svn.html have a error.
On 5/22/07, David Daney <[EMAIL PROTECTED]> wrote: Wei Chen wrote: > i think http://gcc.gnu.org/svn.html have a error. > > "Using the SVN repository > > Assuming you have version 1.0.0 and higher of Subversion installed, > you can check out the GCC sources using the following command: > >svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc " > I think you are mistaken. The command above does in fact check out the source into a directory named gcc. > the right is > > svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk This will work as well, but the workspace will be in a directory called 'trunk' > orsvn -q checkout svn://gcc.gnu.org/svn/gcc/trunk/gcc > That is probably not what you want. That will only checkout the gcc subdirectory. The result while interesting, will not be sufficient to build a working compiler. David Daney I'm using tortosieSVN. it's a visual version with SVN. so the url is svn://gcc.gnu.org/svn/gcc/trunk. forgive me that i didn't know the syntax about SVN in command line that's right. i'm wrong. -- i'm a newbie in GCC community. Wei Chen
Re: http://gcc.gnu.org/svn.html have a error.
Wei Chen wrote: i think http://gcc.gnu.org/svn.html have a error. "Using the SVN repository Assuming you have version 1.0.0 and higher of Subversion installed, you can check out the GCC sources using the following command: svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc " the right is svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk orsvn -q checkout svn://gcc.gnu.org/svn/gcc/trunk/gcc Why do you feel that this is an error? Did you try the command in the form that it was written, and if so, what happened? (It works fine for me.) If you look at the helpfile for the svn checkout command (which you can see if you enter the "svn help checkout" command), you'll see that it has an optional PATH argument, which tells it the name of the directory that it should put the checked-out files into. That's what the "gcc" is in form of the command that's given. - Brooks
