Re: Ada character types : tree code and DW_AT_encoding

the compiler, and that FEs were doing so. > Jim> I think it would be better if the language front ends switched to > Jim> using CHAR_TYPE for character types. Instead of switching away! Right, I guess we need to have the disussion. Andrew.

Re: Lost gccbug submission

> > Daniel Berlin <[EMAIL PROTECTED]> writes: > > | AFAICT (at least according to mail logs, etc) you are the only user of > > apparently, you've to count properly. gccbug is different from what you are using. -- Pinski

Re: Inlining vs the stack

On Aug 12, 2005, at 4:00 PM, Dale Johannesen wrote: Sometimes it matters, as in the original example: c() { char x[100]; } a() { b(); c(); } b() { a(); c(); } Actually in this case, x is removed so it does not matter at all. This case though it does matter: int f(int*); int g(void); in

Re: Inlining vs the stack

> > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Fri, Aug 12, 2005 at 02:16:39PM -0700, Ian Lance Taylor wrote: > > Mike Stump <[EMAIL PROTECTED]> writes: > > > X can be run time selectable, OMF selectable, OS defined... > > > > No. > > > > Making the stack bigger by inlining is no di

Re: C++ vs. pthread_cancel

;re using > pthread_cancel, which is somewhat frowned upon as > inherently unsafe. There is a whole mailing list about this: http://www.codesourcery.com/archives/c++-pthreads/threads.html This has to be done correctly with the C++ standard and POSIX people and the GCC people will be involved but not on the GCC list as it just gets in the way. Thanks, Andrew Pinski

Re: C++ vs. pthread_cancel

een no consensus yet. That is why I mentioned the list. GCC is not going to implement anything until there is a consensus of how to proceed. Thanks, Andrew Pinski

Re: GCC build goes into endless loop

; PR tree-optimization/22236 What is happening here is we were miss-compiling a finite loop to be an infinite loop. Thanks, Andrew Pinski

Re: GCC build goes into endless loop

On Aug 17, 2005, at 11:01 AM, Marcel Moolenaar wrote: On Aug 17, 2005, at 12:09 AM, Gerald Pfeifer wrote: On Mon, 15 Aug 2005, Marcel Moolenaar wrote: I see the same on ia64-hp-hpux11.23, hppa1.1-hp-hpux11.11 and hppa64- hp-hpux11.11. I haven't had time to analyze the problem, though. Do

Re: Keyword _Imaginary in C99 standard and in GCC

On Aug 18, 2005, at 11:04 PM, Yao qi wrote: Hi, everyone, I have looked through C99 standard, in 6.4.1 Keywords, "_Imaginary" is mentioned as a keyword in this standard. However, it seems that GCC can not recognize it, report error: '_Imaginary' undeclared. I also search it in GCC info,

Re: Keyword _Imaginary in C99 standard and in GCC

On Aug 18, 2005, at 11:25 PM, Yao qi wrote: Thanks. That means GCC has not fully support C99, just partialy, am I right? I want to continue a question further, could you tell me where can I find a document about GCC's coverage in C99, if any? http://gcc.gnu.org/c99status.html Note there is

Re: Gcc and a Garbage Collector.

> > Hi, > > With this page from Wikipedia, > http://en.wikipedia.org/wiki/GNU_Compiler_Collection, in the "See also" > section, > there is a sentence about a Garbage collected included in GCC. > > Is it true ? Yes. > If yes, how can I use it with my c++ source code ? (documentation, > artic

Re: Gcc and a Garbage Collector.

On Aug 19, 2005, at 8:16 PM, Stephane Wirtel wrote: It is a very simple mark and sweep GC and not realy useful for most other projects. You mark each struct for GCable and all static and global variables too. You cannot have only a reference to a GCable on the stack (it has to be in a GC

Re: Bootstrap failure on powerpc-apple-darwin8 with Ada

> Sure. So far I don't see a problem though. > > > > IE if we have something very funky like: > > > > static int c; > > static int d; > > static struct foo *a = &{&c, &d}; > > > > (and if you look, andrew found a case wh

Re: GCC 4.1 Status Report (2005-08-21)

On Aug 22, 2005, at 1:27 AM, Mark Mitchell wrote: (Quite a few of the diagnostic messages stem from the design decision to issue warnings from the optimizers...) Only 8 out of 49 at that, though some are very minor as two are just complaining wording of the warning. And almost all are uninit

Re: Assembling pending decls before writing their debug info

This was all caused by Mark's patch to fix PR 18556. This is a regression from 3.4.x. Thanks, Andrew Pinski

Re: GCJ Interpreter Aborts (2005-08-24 IST)

> > > In the last 24 hours, something has gone in which makes > > the GCJ interpreter "gij" abort on even simple "Hello World" > > classes. For example, the "RuntimeCheck" program in > > the Jacks testsuite: > > I had (probably) the same thing yesterday. Here's a backtrace: It was caused by t

SSA_NAMEs not always released

nd see what they can do? This will improve memory usage in GCC and also there will be more SSA_NAME reuse which is good. Thanks, Andrew Pinsk Index: tree-ssa.c === RCS file: /cvs/gcc/gcc/gcc/tree-ssa.c,v retrieving revision

Re: SSA_NAMEs not always released

On Wed, 2005-08-24 at 18:28 -0400, Daniel Berlin wrote: > > Could someone look into this and see what they can do? > > You should probably ask Diego or Andrew directly whether they'd like us > to do this in bsi_remove (which requires adding an argument) and > remove_ph

Re: SSA_NAMEs not always released

On Wed, 2005-08-24 at 21:26 -0400, Daniel Berlin wrote: > On Wed, 2005-08-24 at 19:19 -0400, Andrew MacLeod wrote: > > removing a stmt doesn't mean that the def is no longer needed. > > That ws the goal of the extra argument, however I noticed this after I sent the note :-

Re: RFC - COST of const_double for x86 prevents constant copy propagation in cse

On Aug 25, 2005, at 2:09 PM, Fariborz Jahanian wrote: Compiled with -O1 -mdynamic-no-pic -march=pentium4 produces: pxor%xmm0, %xmm0 movsd %xmm0, 16(%eax) movsd %xmm0, 8(%eax) movsd %xmm0, (%eax) But following code results in 7% performance gain in eon

Re: RFC - COST of const_double for x86 prevents constant copy propagation in cse

On Aug 25, 2005, at 3:59 PM, Fariborz Jahanian wrote: I think the problem may be somewhere else. I got the same xmm0 code sequence on Linux/ia32 with -msse3 -mfpmath=sse. However, I got xorl%eax, %eax movq%rax, 16(%rdi) movq%rax, 8(%rdi) movq%rax

Re: PCH / ObjC issue with gcc 4.0.2-pre

On Aug 26, 2005, at 10:16 AM, Helge Hess wrote: Hi, I'm experiencing some issue with using a precompiled header with an Objective-C file. When including the header, I'll get duplicate symbols, like this: ---snip--- SaxAttributeList.m:188: error: redefinition of 'struct _objc_symtab' SaxAttr

Problem building 3.3.6 (with 3.4.4): xgcc: cannot specify -o with -c or -S and multiple compilations

ons -fdata-sections -c ../../../../gcc-3.3.6/libstdc++-v3/libsupc++/guard.cc -fPIC -DPIC -o guard.o xgcc: cannot specify -o with -c or -S and multiple compilations make[4]: *** [guard.lo] Error 1 Thanks Andrew Walrond

Re: Problem building 3.3.6 (with 3.4.4): xgcc: cannot specify -o with -c or -S and multiple compilations

On Sunday 28 August 2005 16:06, Kean Johnston wrote: > Andrew Walrond wrote: > > Can anybody explain what this error might mean? > > > > /tmp/gcc-3-3.heretix/work/gcc/xgcc "" -B/tmp/gcc-3-3.heretix/work/gcc/ > > ^^^ > &g

Status of --enable-mapped-location

Does anyone know of the status of --enable-mapped-location? I tried to do a bootstrap and test and I got a lot of failures due to getting the wrong line number and file for the error message when dealing with macros. Thanks, Andrew Pinski

Re: Running ranlib after installation - okay or not?

On Aug 31, 2005, at 2:02 PM, Ian Lance Taylor wrote: Gerald Pfeifer <[EMAIL PROTECTED]> writes: Does anyone disagree (and if not, have suggestions how to address this in GCC)? ranlib is basically never required on a modern system. It is really only needed if the archive is built with the S

Re: Running ranlib after installation - okay or not?

On Sep 1, 2005, at 4:10 PM, Joe Buck wrote: On Thu, Sep 01, 2005 at 12:16:23PM +0900, Peter O'Gorman wrote: I would suggest continuing to run ranlib after install, but not failing if it does not work. Won't you then get warning messages on Darwin every time someone tries to use the installe

Re: Problem building 3.3.6 (with 3.4.4): xgcc: cannot specify -o with -c or -S and multiple compilations

kernel; sed (and sometimes other tools like rm) crashes randomly during build when running newer kernel... (same .config, vanilla untainted kernels) I'm going to chase this down on LKML now. Sorry for the noise Andrew Walrond

Re: S/390 Bootstrap failure due to fixup_eh_region_note

On Sep 5, 2005, at 8:27 AM, Andreas Krebbel wrote: Hello Richard, s390 and s390x can't bootstrap with the following patch, because the new assertion introduced with the fixup_eh_region_note function is triggered. Note this is recorded as PR 23711. Thanks, Andrew Pinski

Re: libssp missing from CVS

On Sep 5, 2005, at 11:35 AM, Peter S. Mazinger wrote: Hello! libssp subdir is present in cvs (checked on savannah) but cvs -q upd does not get it. Is it a cvs-server failure or something on my side? You want to update with "cvs -q up -d -P", -d is required to get the new directories. -- P

Re: S/390 Bootstrap failure due to fixup_eh_region_note

On Sep 5, 2005, at 6:39 PM, Richard Henderson wrote: On Mon, Sep 05, 2005 at 02:27:54PM +0200, Andreas Krebbel wrote: (insn 31 29 49 5 (set (mem/s/j:SI (plus:SI (reg/v/f:SI 47 [ env ]) (const_int 4 [0x4])) [0 .ex+0 S4 A32]) (mem/f:SI (plus:SI (plus:SI (reg:SI 55)

Re: S/390 Bootstrap failure due to fixup_eh_region_note

On Sep 5, 2005, at 6:39 PM, Richard Henderson wrote: On Mon, Sep 05, 2005 at 02:27:54PM +0200, Andreas Krebbel wrote: (insn 31 29 49 5 (set (mem/s/j:SI (plus:SI (reg/v/f:SI 47 [ env ]) (const_int 4 [0x4])) [0 .ex+0 S4 A32]) (mem/f:SI (plus:SI (plus:SI (reg:SI 55)

Re: S/390 Bootstrap failure due to fixup_eh_region_note

On Sep 6, 2005, at 3:13 AM, James A. Morrison wrote: Won't this break a disabled checking build since internal_throw will become unused? Yes but this was more of a RFC rather than submitting a patch. -- Pinski

Re: Store-copyprop not very bright

On Sep 6, 2005, at 8:21 AM, Steven Bosscher wrote: Hi, Consider this little snippet: int x; int foo (int a) { x = a; return x + 3; } Likewise for: int foo (int a, int *x) { *x = a; return *x + 3; } -- Pinski

Re: GCC 4.0.2 Status Report

On Sep 7, 2005, at 11:21 AM, Mark Mitchell wrote: Paolo Bonzini wrote: There's no special freeze for the 4.0 branch at this point; we'll leave it in regression-fixes only mode. The branch will freeze when I create the first release candidate. Some of your C++ fixes have been quite invasive.

Re: Question regarding compiling a toolchain for a Broadcom SB1

bound to be rather frustrating. > > Sorry I can't be more helpful, except to say that it is indeed > possible. I wonder if Angela et al.'s magic script that automates all this stuff is still around somewhere. Maybe it'll still work, or maybe someone has an up-to-date copy. Andrew.

Re: var_args for rs6000 backend

efault value for powerpc-linux-gnu is hard floats. Thanks Andrew Pinski

uncaught exception in g++ 3.4 and 4.0

There's a thread at http://groups.google.co.uk/group/gnu.gcc.help/tree/browse_frm/thread/e85dce7d69fb7dc1 which looks odd. It seems that the exception filter is not being correctly processed. I can't find a Bugzilla entry for this. Is it really a bug? Andrew. quot

Re: zero sized initializers with side effects discarded

On Sep 9, 2005, at 8:30 AM, Olivier Hainque wrote: Hello, I have been experimenting with a simple patch adding side effects checks to the conditions, like "! TREE_SIDE_EFFECTS (value)" in init_ctor_eval Yes the one in needs to gimplify only the expression as a statement and not add a modify

Re: zero sized initializers with side effects discarded

the issue correctly. If you could test and post the patch, that would be nice? Thanks, Andrew Pinski ChangeLog: * gimplify.c (gimplify_expr) : Add the expressions to a statement list instead of gimplifying them. Index:

Re: zero sized initializers with side effects discarded

On Sep 9, 2005, at 4:40 PM, Olivier Hainque wrote: Olivier Hainque wrote: I'm not yet clear why the call is not issued there. This is my first dive in the gimplifier, so it might well be simple. FWIW, I think part of the problem is that TREE_SIDE_EFFECTS is not set on the constructor, de

Re: Gcc 4.0.2 RC1 checking not disabled?

nable-checking=release for release branches with building with normal checking on stage1. Thanks, Andrew Pinski

Re: Symbolic replacement

the front-end should be > > the best place to do it. Do I need to do this for each rule in > > c-parse.y ? Is there a more simpler and common way to handle it. ? > > Use ed. If you have line-numbers and variable names that's the easiest. Or use perl, awk, etc. Also c-parse.y does not exist anymore. Thanks, Andrew Pinski

Re: RFA: pervasive SSE codegen inefficiency

ra set helps but does not solve the real issue of the register allocator being stupid. Thanks, Andrew Pinski

Re: RFC: dbxout_type rewrite

his becomes a little mute, like the new cctools and stuff. Thanks, Andrew Pinski

Re: Cost of having an immediate use in the phi argument

put first in the phi_arg_d structure for a different reason, so that we can find the index of a USE that falls in a PHI node if anyone wants it, via phi_arg_index_from_use. Andrew

Re: Gcc 4.1 has been failing SPEC CPU 2000 on 64bit platforms

with enough courage to propose my fix of using memset instead of casting. Thanks, Andrew Pinski

Re: Undefined behavior in genautomata.c?

statically allocated data in genautomata.c: Note this also happens in tree.h with tree_string and a couple more places. Really if it is the last element in a struct, you cannot say what the bounds are. Thanks, Andrew Pinski

Re: constructors and multiple entry points

On Sep 19, 2005, at 1:44 PM, Gabriel Dos Reis wrote: Hi, We're assessing many proposals to add "forwarding constructors" and forwarding functions to C++0x; and I got a question. In standard C++, constructors cannot be recursive functions. I'm wondering whether the multiple entry-point

Re: GCC 4.0.2 RC2

oblem which I will be fixing once 4.1 is branched. Thanks, Andrew Pinski

Re: GCC 4.0.2 RC2

On Sep 19, 2005, at 4:21 PM, Eric Botcazou wrote: Anyways, all of the known failures with the obj-c++ with the GNU runtime have been filed and someone needs to look into them. Are you talking about these? I filed them as bugs, not fixed them. Thanks, Andrew Pinski

Re: Failure to build gcc cvs trunk on cygwin:

On Sep 20, 2005, at 7:47 AM, Christian Joensson wrote: Well... I just happend to shoot off a test build on cygwin... and it barfs like this: anyone else see this or am I just being stupid on my own here? This is PR 21766. -- Pinski

Re: fortran-testcase/dce question

to keep it alive? It should be but from the looks of it. For some reason in alias2, we don't say D.503_30 points to anyoffset in &e unlike before. You might be able to generate a C testcase for this too. Can you also file a bug? Thanks, Andrew Pinski

Re: fortran-testcase/dce question

On Sep 20, 2005, at 11:09 AM, Andrew Pinski wrote: On Sep 20, 2005, at 3:01 AM, Dorit Naishlos wrote: We've had the testcase below in autovect-branch for a while, testing that the 3 loops get vectorized. On mainline the third loop now gets eliminated by DCE (.t44.dce3). Not s

Re: warning about classpath import

. However, IMO each Classpath import is more solid than the previous one as bugs get fixed, so I'm in favour. But a radom cut of Classpath HEAD is perhaps not so stable. Hmm. Discuss... Andrew.

Re: [RFC] patch to fix an ICE involving sign-extract of mmx expression

On Sep 22, 2005, at 4:21 PM, Fariborz Jahanian wrote: Following patch avoids this problem. If this is OK, I will submit a patch when fsf mainline is unfrozen. The FSF mainline is not frozen, only the 4.0 release branch. Thanks, Andrew Pinski

gcc-4.0.2: supporting -fvisibility for solaris ld

discarded? Sorry for the length, or if this is all somehow way off base; I'm new to gcc internals... Thanks, Andrew

Re: Question about the use of builtins in altivec.h

rewrite for 4.1.0 for the altivec.h header which should improve this. And also in both 4.0.0 and 4.1.0, there is autovectorization which should expose more bugs. Also sometime during either 3.4.0, 4.0.0, or 4.1.0, an altivec testsuite was addded. Thanks, Andrew Pinski

Re: Aliasing violation generated by fold_builtin_memcmp?

On Sep 29, 2005, at 8:32 PM, Daniel Berlin wrote: Any suggestions how to fix this? The easiest thing is to store a version of unsigned_char_type_node somewhere that has it's TYPE_ALIAS_SET set to 0, and use it there. Whether this is the best solution, i'll leave to others :) Something li

Re: gcc -I- feature

On Sep 30, 2005, at 8:46 PM, Neil Booth wrote: nmake Technical Support wrote:- This is to request reinstatement of the -I- command line directory search option. Sorry for the late request, we only recently became aware that -I- is deprecated in gcc 4.0. I agree this should not be removed (

Re: RFC: redundant stores in C++

On Oct 1, 2005, at 5:54 PM, Dale Johannesen wrote: In C++, when we have an automatic array with variable initializers: void bar(char[4]); void foo(char a, char b, char c, char d) { char x[4] = { a, b, c, d }; bar(x); } Testsuite passes with this but I can believe improvements are possibl

Re: Wishlish: GCC option for explicit booleans

> > C++ would be a better language if the boolean type did not implicitly > convert from int. For example, many novice programmers make the > mistake. > >if (i = j) dosomething(); // Should be i == j > > If conversion to boolean required explicit this would all be solved. It > would mean all

Re: RFC: redundant stores in C++

On Oct 1, 2005, at 11:10 PM, Dale Johannesen wrote: But better fix would be not call split_nonconstant_init_1 for local decls and have the front-end produce a CONSTRUCTOR which is just like what the C front-end produces. I'll try it. This patch should fix the problem and also fixes FSF PR

Re: [URGENT] GCC 4.0 Nomination

involved in gcc here in the UK. I'm not sure how you'd choose someone, given that gcc is a collective effort. Andrew.

Re: Fishy build system: make_exports.pl called on darwin?

> > 6) Is this whining reporting significant information, for the > > person that wants to fix the bug? > > Well on the system in question ppc-apple-darwin-7.8.0 the perl script > in question simply doesn't work. Since there doesn't appear to be > much in the way of it inside acinclude.m4 it

Re: Should -msse3 enable fisttp

should not be disabled by -mno-sse3 flag." And then RTH agreed: http://gcc.gnu.org/ml/gcc-patches/2005-03/msg01432.html So from the sound of it fisttp is not a SSE3 instruction. Thanks, Andrew Pinski

Re: Should -msse3 enable fisttp

Thanks, Andrew Pinski

Re: RFC: IPO optimization framework for GCC

> > I have been given some time by my management to work on creating a > framework for IPO optimizations in GCC by creating an intermediate file > reader and writer for GCC. > > I would like to start by getting any input and advice the members of the > GCC community might have for me. I would al

Re: [obj-c++] a few current test suite failures

On Oct 9, 2005, at 3:40 AM, Christian Joensson wrote: In http://gcc.gnu.org/ml/gcc-testresults/2005-10/msg00348.html, there's a few obj-c++ failures. Here's a posting of the log file for them: I have report all of these already. -- Pinski

Re: Mainline now closed to all changes which do not fix regressions

On Oct 12, 2005, at 9:49 AM, Adriaan van Os wrote: Mark Mitchell wrote: As previously announced, here: http://gcc.gnu.org/ml/gcc/2005-10/msg00093.html the mainline is now subject to the usual release-branch rules: only fixes for regressions. The development rules at

Re: Need advice: x86 redudant compare to zero

"ix86_match_ccmode (insn, CCGOCmode) && ix86_binary_operator_ok (MINUS, SImode, operands)" "sub{l}\t{%2, %0|%0, %2}" [(set_attr "type" "alu") (set_attr "mode" "SI")]) Maybe adding a pattern like that, will work? You most likely would like to "steal" other patterns like that from the rs6000 backend. Thanks, Andrew Pinski

Re: Severe problems with vectorizing stuff in 4.0.3 HEAD

On Oct 14, 2005, at 3:11 PM, Kean Johnston wrote: All, I am getting a lot of test suite failures with almost all of the vect/* tests. I am using pr18400.c from the test suite as an example here, becuase its about the smallest one I can find. Here is what is generated at -O2: Can you just fi

Re: Severe problems with vectorizing stuff in 4.0.3 HEAD

-fno-optimize-sibling-calls and see if that works? If so, then the problem is that we sibling calls should not be done in main. To fix the testcase anyways to be correct is to put "return 0;" after the call to main1. Since right now the return of main could be anything. Thanks, Andrew Pinski

Re: Severe problems with vectorizing stuff in 4.0.3 HEAD

On Oct 14, 2005, at 3:43 PM, Kean Johnston wrote: What does the fact that -fno-optimize-sibling-calls worked indicate really? Without that option something really does seem to be mis-calculating the stack offsets by 4. What may be of interest here is that aside from the vect/* tests, the only o

Re: Severe problems with vectorizing stuff in 4.0.3 HEAD

On Oct 14, 2005, at 3:55 PM, Andrew Pinski wrote: On Oct 14, 2005, at 3:43 PM, Kean Johnston wrote: What does the fact that -fno-optimize-sibling-calls worked indicate really? Without that option something really does seem to be mis-calculating the stack offsets by 4. What may be of

Re: Severe problems with vectorizing stuff in 4.0.3 HEAD

On Oct 14, 2005, at 4:43 PM, Kean Johnston wrote: It indicated that sibling calling optimization in main should be disabled for targets that need to up the stack alignment, otherwise you get the stack alignment of a lower one than While that may be true, I think the problem is broader. This

Re: Updating a subversion directory?

On Oct 18, 2005, at 1:44 PM, Steve Kargl wrote: So, I finally get a copy of mainline, yesterday. As user [EMAIL PROTECTED], I did The svn repro is not being updated with every commit to cvs. What you can do is checkout two copies and commit something to svn and then update the other copy.

Re: Updating a subversion directory?

On Oct 18, 2005, at 3:05 PM, Steve Kargl wrote: We went over this yesterday. Until Tobi fixed the wiki it said to use svn co svn+ssh://gcc.gnu.org/svn/gcc/trunk Well it is correct for most people and to me it looks like a standard URI/URL so most people would just add username@ by themselves

Re: A couple more subversion notes

any changes and check it back in that's where the changes will go. But "svn ls branches" says 105358 dberlin Oct 16 01:53 gcc-4_0-branch/ So, how on Earth do I go from "105366 104478" to gcc-4_0-branch ? Andrew.

Re: A couple more subversion notes

ill > > go. > > svn info ChangeLog Aah, that's the key. Where we have one command in CVS, "status", which tells us which branch a file is on and its status, we now have two separate commands, "status" and "info". Easy enough, once you know... Andrew.

Re: A couple more subversion notes

s, or should we just not move? > > Again, there are invariably some pains associated with any switch in > workflow :) I've been browsing gcc change sets, and I have to say it's very nice feature! I'm in favour of the change if we can get a decent ssh tunnelling solution sorted out so that "svn diff" is decently fast. Andrew.

Re: RFC: future gfortran development and subversion

On Oct 19, 2005, at 4:36 PM, FX Coudert wrote: A regression is a bug that was not in release N - M and was discovered in release N. You are then free to fix N - M + 1 to N. Like you have a testcase that crashes gfortran on 4.1.0, but did not on 4.0.2. But then, you'll explain people that th

Re: A couple more subversion notes

Giovanni Bajo writes: > Gabriel Dos Reis <[EMAIL PROTECTED]> wrote: > > > I'm looking forward to solutions that lower the entry barrier, > > specifically with repect too OpenSSH, diff and svk. > > > I'm going to write something in the wiki about svk. There's much FUD > spreading > in t

Re: A couple more subversion notes

SSH connection caching solves the slow connection problem with very little setup cost. It's not worth making a fuss about. Andrew.

Re: A couple more subversion notes

ns are made, but they are simple TCP connections with little overhead. Were there no caching I would be strongly opposed to using Subversion but with it I have no objection at all. Andrew

Re: Vectorizing HIRLAM 2: One out of the "unhandled data-ref" garbage bin :-)

On Oct 21, 2005, at 9:19 AM, Toon Moene wrote: L.S., This code: SUBROUTINE S(A, B, N) DIMENSION A(N), B(N) READ*,Z,B DO I = 1, N A(I) = Z * B(I) ENDDO PRINT*,A END when compiled thusly: The problem here is not really related to the vectori

Subversion access via http proxy

go back a few versions now. Is there any equivalent for the new gcc.gnu.org repository? I tried anoncvs and anonsvn, among others. If so could somebody put it on the wiki. Thanks. Andrew Stubbs P.S. The wiki page seems to have got a little confused. It used to have three different examples

Re: regression hunt setup using Subversion

On Oct 21, 2005, at 3:11 PM, Joseph S. Myers wrote: The use of ncpu=`grep '^processor' /proc/cpuinfo | wc -l` seems Linux-specific; this looks like it should be in gcc-svn-env as a default for the user to customise, rather than in bin/gcc-build-*. I don't think it is Linux specific, it wor

Re: RFC: future gfortran development and subversion

The following 2 bugs have patches submitted: On Oct 21, 2005, at 5:06 PM, Paul Thomas wrote: 19425 Duplicate SAVE attribute problem - illegal f95 and questionable f77 22282 loc intrinsic and %loc construction is not implemented in gfortran - do-able but not a disaster. -- Pinski

Offline

soon. Thanks, Andrew Pinski

Re: GGC Questions

is not managed by the garbage collector, but is contained in a structure which is. The garbage collector insists on being made aware of whats in the structure in this case. The operand cache is managed separately, and completely disposed of when ssa is free'd. It is included in other structures, such as tree_ssa_name which *is* garbage collected. The skip tells the garbage collector to ignore any memory pointer to by ssa_use_operand_t since it isn't GC managed. Andrew

Re: backslash whitespace newline

> > > OK, so it must be this, then > > Installed. > > That works. Thanks. >

Re: backslash whitespace newline

> > > On Oct 24, 2005, at 3:52 PM, Neil Booth wrote: > > > Howard Hinnant wrote:- > > > >> I've been reviewing the age-old issue of interpreting > >> * as the end-of-line indicator as is the current > >> practice with gcc. > > > > FWIW I support abandoning this behaviour too. > > I filed bugzil

Re: backslash whitespace newline

> > > > > > OK, so it must be this, then > > > > Installed. > > > > That works. Thanks. > > Ignore this, this was a typo. -- Pinski

Re: backslash whitespace newline

> > > > > > > On Oct 24, 2005, at 3:52 PM, Neil Booth wrote: > > > > > Howard Hinnant wrote:- > > > > > >> I've been reviewing the age-old issue of interpreting > > >> * as the end-of-line indicator as is the current > > >> practice with gcc. > > > > > > FWIW I support abandoning this behaviour

Re: backslash whitespace newline

> > > > > Oh, one more thing. This seems like the normal problem of not > > reading the docs > > if something does not work the way you want it to work. > > So? > > > The only thing we can do is point it out that it is documented > > behavior and > > then move on to the next issue. Also wh

Re: backslash whitespace newline

> > On Oct 25, 2005, at 6:22 PM, Andrew Pinski wrote: > > > We have people already complaining about removing extensions. Why > > should we change > > this implementionation defined documented behavior. > > I'm not convinced that "extension"

Re: backslash whitespace newline

> > On Oct 25, 2005, at 7:44 PM, Andrew Pinski wrote: > > > But this is not an extension at all. This is an implementation > > defined > > behavior which is different than what an extension would do. > > > > People depending on this is not the correct

Re: backslash whitespace newline

> > On Oct 25, 2005, at 4:44 PM, Andrew Pinski wrote: > > People depending on this is not the correct thing do any ways as > > there could be another compiler besides which GCC which does this. > > Let's enumerate them, what other compilers do this besides

Re: backslash whitespace newline

> > On Oct 25, 2005, at 4:25 PM, Joe Buck wrote: > > I'm having a hard time picturing source code that > > > > a) exhibits different behavior because of this bug, and > > b) is maintainable (remember, the behavior depends on the presence > > of characters that are completely invisible to man

<    3   4   5   6   7   8   9   10   11   12   >