On Jul 27, 2005, at 2:18 PM, Richard Henderson wrote:
On Tue, Jul 26, 2005 at 11:10:56PM -0700, Dale Johannesen wrote:
Yes, it is. The following fixes my problem, and causes a couple of
3DNow-specific regressions
in the testsuite which I need to look at, but nothing serious; I think
it's gotten
"Ioannis E. Venetis" <[EMAIL PROTECTED]> writes:
> Sorry for the late response. Before creating the bug report I though I
> should search the bugs database and I found that a comment for bug
> 13756 mentions the missing documentation for -ftree-dse
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Northcott wrote:
| On 30/07/2005, at 1:06 AM, Jack Howarth wrote:
|
|>Well the gcc4.info for the package containing gfortran in fink has...
|
| The only thing I needed to add was gmp, which built from the source
| without problems.
|
| The c
On 30/07/2005, at 1:06 AM, Jack Howarth wrote:
Well the gcc4.info for the package containing gfortran in fink
has...
Depends: gmp-shlibs (>= 4.1.3-11), cctools (>= 576-1) | odcctools
(>= 576-200503
27), %N-shlibs, libiconv
BuildDepends: gmp (>= 4.1.3-11), libiconv-dev
which is a tad con
That's a pretty neat trick.
I know, we've filed a patent for it, wait for it, no, wait, ok, just
kidding... :-)
Hehehehe :)
I dont suppose I could trouble you to give me the voodoo required for
inserting an extra pushl before the call could I?
Not sure exactly what you want, but with
On Friday, July 29, 2005, at 01:23 PM, Kean Johnston wrote:
[ cough ]
#if _FILE_OFFSET_BITS - 0 == 32
int open (const char *, int, int) asm ("open32");
#elif _FILE_OFFSET_BITS - 0 == 64
int open (const char *, int, int) asm ("open64");
#else
int open (const char *, int, int) asm ("__open");
#e
[ cough ]
#if _FILE_OFFSET_BITS - 0 == 32
int open (const char *, int, int) asm ("open32");
#elif _FILE_OFFSET_BITS - 0 == 64
int open (const char *, int, int) asm ("open64");
#else
int open (const char *, int, int) asm ("__open");
#endif
That's a pretty neat trick. I dont suppose I could
tr
Hi !
I would like to port IDL language (language for
describing the interfaces) to gcc and also create a
several backend compilers. Since the interface is not
complete implementation it wont be possible to produce
final executable after IDL parsing. Also as far as I
can see IDL is heavily reduced
* michael meeks:
> I've been doing a little thinking about how to improve OO.o startup
> performance recently; and - well, relocation processing happens to be
> the single, biggest thing that most tools flag.
Have you tried prelinking?
Hi there,
I've been doing a little thinking about how to improve OO.o startup
performance recently; and - well, relocation processing happens to be
the single, biggest thing that most tools flag.
Anyhow - so I wrote up the problem, and a couple of potential
solutions / extensions
Ioannis E. Venetis wrote:
I found that a comment for bug 13756
mentions the missing documentation for -ftree-dse
Should I still create a new bug report?
No. Since we already have one, we don't need another one.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
On Fri, Jul 29, 2005 at 11:05:56AM -0400, drizzle drizzle wrote:
> Here is the patch, an header file, the test case. The only thing I
> need is be able to insert a function call inside
> linear-loop-transform. The error message I get is
>
> main.c:15: internal compiler error: in var_ann, at tree-
On Fri, Jul 29, 2005 at 10:27:21AM -0400, drizzle drizzle wrote:
> Could it be that it being done lower in the pass unlike insertions in
> tree-profile, gomp - some ssa defintion information is missing. The
> reason I have been led to think is because it fails
> register_new_defintions. I would a
Could it be that it being done lower in the pass unlike insertions in
tree-profile, gomp - some ssa defintion information is missing. The
reason I have been led to think is because it fails
register_new_defintions. I would appreciate any suggestions.
thanks
On 7/28/05, drizzle drizzle <[EMAIL P
On 28 Jul 2005, Joe Buck announced authoritatively:
> Glad you found this. Your experience is why I've always objected when
> someone suggests a .gccrc or a GCC_OPTIONS environment variable or the
> like; people will forget that they have such files and report
> unreproducible bugs.
Instead, peop
Hello again,
Sorry for the late response. Before creating the bug report I though I
should search the bugs database and I found that a comment for bug 13756
mentions the missing documentation for -ftree-dse
(http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13756#c8).
Should I still create a new b
Hello-
I'm hoping to network with you and find out if you know anyone who
you think could be interested in the following opportunity?
Sr. Compiler Engineer
Position Type: Full-Time Employee
Location: San Jose, California (Silicon Valley, USA)
Generous Compensation and Stock package
--
Mark,
- with your commit for PR 20142, you also committed a hunk to name-lookup.c
which is not described in the ChangeLog. It is also unclear whether it is
effectively need for that PR or not, but nonetheless it went in, so the entry
should probably be fixed.
- It is unclear which patch fixed PR
18 matches
Mail list logo
