wrong?
hope to see your suggestion/advice again, and thanks a lot in advance,
Eric
-
On Fri, 2011-06-10 at 22:18 -0400, bs wrote:
> On 6/10/2011 9:43 PM, eric wrote:
> > Dear Bjarne Stroustrup:
> >
> >I copied a piece
article,
and download fltk-1.3.x-r7769
re autoconf
./configure
make
sudo make install
then recompile
e...@eric-laptop:~/BStrou/usingC++4/code/Chapter12$ g++ -Wno-deprecated
chapter.12.7.2.cpp -lfltk
In file included from chapter.12.7.2.cpp:7:
Simple_window.h:17: error
e this is a configure-time option only.
[2] describes GCC SJLJ, which is not the same as GNAT SJLJ.
--
Eric Botcazou
was somehow suspecting that gnat1 supports both ZCX and SJLJ, looks in
> system.ads, and decides what kind of assembly code it needs to emit based on
> that. Am I correct?
Yes, you are.
> In that case, I need just one compiler and two libgnats, right?
Right.
--
Eric Botcazou
Has this been considered in the past, but rejected for some reason?
Don't see why it would. Could be useful.
Should I have posted this to a different GCC list? :P
This is fine.
-eric
o True in system.ads).
> Eric, how difficult would it be to backport a fix from 4.2 to 4.1?
Too invasive I'd think.
--
Eric Botcazou
g abi or if we can depend on all changes not breaking the abi
of these libraries?
Thoughts? Comments? Plans? Assurances?
-eric
On Oct 19, 2006, at 2:50 PM, Diego Novillo wrote:
Eric Christopher wrote on 10/19/06 17:33:
I was wondering if anyone planned on changing abi or if we can depend
on all changes not breaking the abi of these libraries?
There is nothing planned in that area, but I wouldn't want to
guar
with plain "make" (i.e. doesn't screw up the build
directory), I don't see a reason not to move it. You'd do "make"
anyway to check if a dependency is missing, wouldn't you?
Really, all I care about is having it depend on the languages enabled.
It's driving me crazy at the moment on a non-fortran build.
-eric
../
some-prefix, but it should be consistent in how it looks for libraries
and headers.
Thoughts?
-eric
inline, or to revert it in the same way.
Exactly my position. :-)
> Also, having patches on mainline and not a release branch can cause
> quite a bit of confusion. Witness what happend with PR 28243, where I
> fixed something on mainline, but it was not directly approved for a
> relea
release
branch sooner than later?
> I think one source of the problem is that standards the that I hold
> myself to, may potentially be unrealistic for many contributors.
Definitely. I'd say that the patches you review are not your babies, only
those you write are. :-)
--
Eric Botcazou
> since p is a global variable, it can be used in other functions. Any
> other causes?
The first thing to do is to post a reproducer. As Ian said, your code doesn't
even compile...
--
Eric Botcazou
siderably, improving compile times at the expense of lost
aliasing precision. */
maybe_create_global_var (ai);
We have found this to be quite helpful on gigantic elaboration procedures
generated for Ada packages instantiating gazillions of generics. We have
actually lowered the threshol
y
will not be able to disambiguate memory accesses it would have been able to,
if the limit were not reached.
> it is also not really partially disabling. It's really fully disabling
> in 99% of
Partially because it only affects call-clobbered variables IIUC.
--
Eric Botcazou
I ended up including both your preference and mine. Hopefully one or
other other (or both) end up being useful to users.
Thanks, this will help with some of the questions I received
internally today.
-eric
n with gmp/mpfr as
well as c99 inlining. File a bug or bring a problem up for discussion.
As far as 4.2 this is the first I've heard of it. What's the problem?
-eric
On Nov 6, 2006, at 8:59 PM, Andrew Pinski wrote:
On Mon, 2006-11-06 at 20:57 -0800, Eric Christopher wrote:
As far as 4.2 this is the first I've heard of it. What's the problem?
Well you need a new cctools which does not exist for 10.2.
While I'm sure you could be less
s required.
That may not be a bad idea.
Oh and 10.0, 10.1, 10.2 compiling with GCC are all broken (so is
10.3).
I'd probably suggest at least 10.3.9 myself. I'm not sure since 10.3.x
predates
my employment at apple, or what the current policy is regarding it.
-eric
On Nov 7, 2006, at 5:24 AM, David Edelsohn wrote:
Eric Christopher writes:
Eric> We're in stage1, breakages happen - see the current fun with
gmp/mpfr as
Eric> well as c99 inlining. File a bug or bring a problem up for
discussion.
Yes, breakage happens in Stage 1, b
Eric> Well, yes, did you see anything in what I wrote that argued
differently?
Yes, what I quoted, the comparison with gmp/mpfr and c99 inlining.
Those other problems are irrelevant.
I disagree, they were other examples of breakages.
-eric
C
> notices this later, and dies.
See PR rtl-optimization/29329 for a variant.
> Ideas?
The combiner already knows how to update liveness information in some cases
(lost REG_NOTEs) so I think that we probably need to extend this mechanism.
--
Eric Botcazou
> The problem is presumably arising from the REG_EQUAL notes. Where are
> those being generated? Why does this case not arise for other targets?
If the problem stems from REG_NOTEs, then it may again be a duplicate of PR
rtl-optimization/25514.
--
Eric Botcazou
> But note this is with RTL checking enabled (--enable-checking=rtl).
Can anyone refresh my memory: why is RTL checking disabled on the mainline?
--
Eric Botcazou
Andrew's suggestion seemed reasonable too.
-eric
increased in speed many times since then. (Although
sometimes I feel
Kaveh> like bootstrapping time has increased at an even greater pace
than chip
Kaveh> improvements over the years. :-)
I object.
Any reason other than the obvious "I don't want bootstrap time to
increase"?
-eric
> Because it takes a LONG time.
Figures? Tree checking is not cheap with GCC 4.x either.
--
Eric Botcazou
d on.) At 5
> minutes each it adds up fast!
> http://gcc.gnu.org/ml/gcc-testresults/2006-11/msg00294.html
This happened at some point during 4.1 development too. It turned out to be a
code generation bug that was butchering the PTHREAD_* initializer macros.
--
Eric Botcazou
min
assert,runtime,misc,gc: 186 min
assert,runtime,misc,gc,tree:203 min
assert,runtime,misc,gc,tree,rtl,rtlflag 266 min
So I was wrong, tree checking is still relatively cheap; misc and rtl are not.
--
Eric Botcazou
You appear to have regenerated configure, on both mainline and 4.2
branch,
with autoconf 2.60. Could you please regenerate it with 2.59 in both
places?
Sure, I'll have to dig it up somewhere. It appears to be the default
on FC6, I'll use that.
-eric
On Nov 14, 2006, at 11:32 AM, Eric Christopher wrote:
You appear to have regenerated configure, on both mainline and 4.2
branch,
with autoconf 2.60. Could you please regenerate it with 2.59 in both
places?
Sure, I'll have to dig it up somewhere. It appears to be the default
o
build java fine with --disable-multilib
on Intel Darwin. Why don't you try to get that patch into
gcc trunk now that gcc 4.2 has branched?
Yup. You should just be able to commit it now.
-eric
You could always equate the macro to some inline assembly like what is done
for a number of avr-libc macros.
Eric Weddington
> -Original Message-
> From:
> [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> org] On Behalf Of Shaun Jackman
> Sent: Friday, November 17,
e able to recognise these
> idioms without
> using the builtin, but AFAIK that's not been implemented yet.
Plus there is a long lead time between when it is implemented on HEAD, then
branched, released from a branch, and then when it shows up in binary
distributions.
Eric Weddington
> -Original Message-
> From: Steven Bosscher [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 19, 2006 3:55 AM
> To: Eric Weddington
> Cc: Paul Brook; gcc@gcc.gnu.org; Shaun Jackman;
> avr-gcc-list@nongnu.org
> Subject: Re: [avr-gcc-list] Re: AVR byte swap optim
It isn't only on the AVR that bswap_32() is nontrivial to get
right.
These two versions would rule on the i386 if GCC would be just a
little bit
smarter:
I prefer the single instruction bswap that we now generate for
__builtin_bswap[32,64] myself...
-eric
e for this
> case?
The test needs to check that --gc-sections works, so indirectly invoking
ppc64_elf_gc_mark_hook seems to be unavoidable. You could try to tweak the
contents of the sections if you understand why ppc64_elf_gc_mark_hook loops.
--
Eric Botcazou
> This patch introduces canonical types into GCC, which allow us to
> compare two types very efficiently and results in an overall
> compile-time performance improvement.
Please avoid cross-posting, patches should go to gcc-patches@ only.
--
Eric Botcazou
s case, whether it is
> an assembler or linker bug, and whether there is a workaround?
... if the user is trying to link objects files assembled by the GNU assembler
using the Sun linker.
--
Eric Botcazou
> I have built a static runtime library and i want the linker to access
> it automatically without having to pass it explicitly.
Wrong list, this one is for GCC development, not development with GCC.
Try [EMAIL PROTECTED] instead.
--
Eric Botcazou
> Yes, congratulations Richard!
Auf Deutsch, bitte! :-)
--
Eric Botcazou
ith Jack,
other than the failures with isfinite for long double and a couple
of other things darwin is remarkably clean in this situation.
-eric
ular fortran problem.
Oh good. I'd realized I'd used an older checkout earlier and was
having to rerun them. Glad everything seems ok.
-eric
ts) seems to take
> ages.
Right, this seems to be noticeably slower with 4.2, especially libstdc++.
--
Eric Botcazou
should be passed to the configure
line of GCC itself and the compiler entirely rebuilt.
--
Eric Botcazou
> So, my question is this: Do I need to have libgmp and libmpfr
> available as both 32 and 64 bit variants?
No if you use only one compiler (i.e. the multilibbed 32-bit compiler).
--
Eric Botcazou
info (4, precision(0.0_4), range(0.0_4)), &
real_info (8, precision(0.0_8), range(0.0_8)), &
real_info (10, precision(0.0_10), range(0.0_10)) /)
or something along these lines.
--
Eric Botcazou
> but again I got into troubles
libgfortran/selected_real_kind.inc is also generated.
--
Eric Botcazou
mpfr should be multilibbed :)
Yes, that works, at least on x86-64/Linux.
--
Eric Botcazou
/
libiberty.a
ld: warning prebinding disabled because of undefined symbols
ld: Undefined symbols:
_integer_nonzerop
_integer_zerop
This was seen on a few platforms. I think it's due to zdenek's patch.
-eric
be able to audit
without compiler assistance.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG wit
ng Paul Eggert's
cleverness to spark your own gigantic thread? :-) Certainly, doing a mere
build with "make" and a complete bootstrap with "make bootstrap" was rather
reasonable, but you and other build machinery wizards convinced us that this
would be a pain to su
> Not much. I'm convinced it would be feasible, but definitely not easy,
> so I wanted to see how much interest there was - seems like some, but
> not a lot.
Would this comprise retrofitting the support into the 4.2 branch?
--
Eric Botcazou
either automatic bootstrap is a good feature and
we're done, or it (after all) isn't and no series of compilers should be
released with it.
--
Eric Botcazou
> I'd like to see it closed, too, all Linux/BSD vendors I know of are either
> still using 3.x or have switched to 4.1 already.
Yes, 4.1.x seems to have been selected by various vendors as the codebase for
their first GCC4-based release.
--
Eric Botcazou
is that you apparently successively replied
to the previous post, which means that all the patches are tied to a single
gigantic thread in my mailer. :-(
--
Eric Botcazou
ny case of a bug being _closed_
> just because the platform is not a primary one.
Neither can I.
--
Eric Botcazou
c (in gcc 4.3 perhaps) or will
we always use separate subdirectories for 32-bit and
64-bit shared libraries?
All of that is done by a script that calls configure and post-processes
the resultant builds with the exception of libgcc which is built fat
in either place.
-eric
> The reaction varies with developer. AIX continues to use
> xcoff/stabs. The feedback of AIX users to IBM sales representatives and
> executives will determine the response.
FYI Sun has switched to DWARF-2 by default in Studio 11. Just to put a bit of
pressure on you. :-)
On Jan 13, 2007, at 8:28 AM, Jack Howarth wrote:
Eric,
So will FSF gcc on Darwin maintain the current 64-bit subdirectory
or will it eventually migrate to using fat binaries as Apple gcc does?
Current is likely.
-eric
rnings (entity, Off). The problem of suppressing
warnings for a whole given portion of code is of course more complex.
--
Eric Botcazou
. If you somehow manage to build enough trees so
that you can then lipo and get all four architectures together (ok,
this only takes 2 trees), then the symlink will be correct.
-eric
> There's a later ;) simley in the mail and maybe you missed one after
> the second paragraph. (certainly you did)
Then I guess the question is: what is the scope of a smiley? Does it
retroactively cover all the preceding sentences, including the subject?
--
Eric Botcazou
> libcpp/files.c:1238 seems to be a call to memcpy. I don't see
> anyplace a floating point exception might come from. I've certainly
> never seen anything like that.
Division by zero somewhere?
--
Eric Botcazou
> make STAGE1_CFLAGS="-O"
> BOOT_CFLAGS="-march=i686 -O2 -pipe -fomit-frame-pointer -U_FORTIFY_SOURCE"
> profiledbootstrap
Do not set STAGE1_CFLAGS, you may run into bugs of the bootstrap compiler.
--
Eric Botcazou
> And I am still getting floating point exception even with a bare make. Any
> way to debug this?
Not easily unless you already know the innards of the compiler, I'm afraid.
--
Eric Botcazou
mkheaders.conf
> /bin/sh: : cannot execute
> /bin/sh: /]*/../,, -e ta: not found
> sed: Function s,[ cannot be parsed.
That should not happen on Solaris if you set CONFIG_SHELL=/bin/ksh as
recommended in http://gcc.gnu.org/install/specific.html#x-x-solaris2
--
Eric Botcazou
might be missing something but I'm uncertain as to why you'd
want to do this.
-eric
to do this,
but it seems to be used for all of rs6000 as well. Whee.
Anyhow, I can see how it would be bad. Not sure how to handle it
without breaking
how abi stuff is handled for darwin.
-eric
> This patch bootstraps and passes make check on x86_64.
Please do not cross-post. Patches should go to gcc-patches@ only.
--
Eric Botcazou
t; release, most appear not.
The -fpic/-fPIC failures are a little annoying but other platforms probably
have similar glitches, so we can live with them (I personally don't test
with -fpic/-fPIC so I have only the above 2 failures in my logs).
Results on other versions of Solaris are on par with those on Solaris 10.
--
Eric Botcazou
correct
> problems in these patches: the choices will be only to keep the patches
> checked in or to take them out entirely.
What about the patch for PR other/27843 then?
--
Eric Botcazou
> Furthermore, I am not really sure that the FSF testing
> infrastructure is setup to deal with tests of hundreds
> of thousands of lines of code.
Right, this is not the "spirit" of the GCC regression testsuite.
We instead strive to distill reduced testcases from these
> FWIW, in Apple distributed GCC 4.0.x, strict-aliasing is disabled by
> default when -O? is used because it breaks too much existing
> code (not just Apple internal code).
Much more than in 3.x?
--
Eric Botcazou
> I could say much more (there are interesting stories about the
> behind-the-scenes politics) but it's off-topic.
Please think about writing a book telling the whole story when the dust will
have settled. :-)
--
Eric Botcazou
revision 121686:
real251m52.693s
user234m39.234s
sys 12m8.914s
revision 122521:
real687m3.830s
user374m37.001s
sys 19m26.378s
[EMAIL PROTECTED]:~/build/gcc/native> gcc/xgcc -v
Using built-in specs.
Target: x86_64-suse-linux
Configured with: /home/eric/svn/gcc/configure x86_6
terday... sorry for the noise.
--
Eric Botcazou
4.1.x though.
--
Eric Botcazou
ng on them, I imagine that it won't be until they're
done in Leopard, but I'll let him give more information.
-eric
putc (c2, stdout);
int i3 = uc2 & 0x3f;
char c3 = (feof (in)? '=': s [i3]);
putc (c3, stdout);
}
fclose (in);
return 0;
}
If anyone can shed some light on the strange behavior in the C++
program,
I would appreciate it very much.
Thanks,
Eric.
this out further, can someone explain to me why
using TABs is preferrable, as they are interpreted, while spaces are
unambiguous?
Not everyone uses emacs, vi, , or even GNU/Linux...
Eric
d wouldn't
be an inconvenience.
-eric
t decipher.
Don't worry about that :) Basically it's depending things based on other
command line options by default. If, however, you always set it then you
should be fine there. I wouldn't set it for developing gcc, just using
gcc to develop some other application.
-eric
On Mar 17, 2007, at 4:15 PM, Dominique Dhumieres wrote:
Eric,
Thanks for the explanations.
The idea, I believe, is that the default will be the system that you
are currently on.
It would be nice, but it is not the way it seems to work (at least
for gcc,
for g++ and gfortran it may, but
-59.c and
friends which do not pass for the 20070316 snapshot, it is
far from obvious that it is working. Is there a direct way
to check it?
It's not yet checked in :)
-eric
../../../gcc-4.2.0-20070316/fixincludes/fixincl.x:7597: warning:
string length '575' is greater than the length '509' ISO C89
compilers are required to support
Are these expected?
Yup.
-eric
p:6: error: could not convert 's.S::v' to 'bool'
test02.cpp:6: error: in arguument to unary !
Is this a bug or new behavior? If the latter, what is this attributed
to?
Thanks,
Eric.
> 2006-02-07 Eric Botcazou <[EMAIL PROTECTED]>
> config/sol26.h (CPP_SUBTARGET_SPEC): Accept -pthread.
> doc/invoke.texi (SPARC options): Document -pthread.
It's only an alias for the existing -pthreads, not worth mentioning IMO.
--
Eric Botcazou
> So why is it there? Compatibility with some other compiler?
To work around some laziness in libgomp. :-) Other platforms only have
-pthread it seems.
--
Eric Botcazou
my list.
Please note that I am *only* interested in bugs that affect, or may affect,
the AVR port at this time. I have no desire to mess around with bugs that
involve other areas.
Thanks for your time,
Eric Weddington
at it's rooted at / instead of $(slibdir)/.
-eric
Index: Makefile.in
===
--- Makefile.in (revision 123700)
+++ Makefile.in (working copy)
@@ -99,7 +99,7 @@ all: all-multi
# in-tree libraries, and DejaGNU) know about the layo
at the code too :)
-eric
a problem until we shipped a linker that uses
libstdc++.
I'm looking into it when I get a chance.
-eric
quality is deemed sufficient. If it takes longer to do a
release then so be it. Politely point out what is left to get done. The
status reports are a helpful reminder of the state of the branch.
Eric Weddington
> -Original Message-
> From: Kenneth Hoste [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 17, 2007 3:23 AM
> To: gcc@gcc.gnu.org
> Subject: GCC -On optimization passes: flag and doc issues
> - finline-functions is enabled at -Os, but isn't listed so
And it seems to have some issues:
> -Original Message-
> From: Steven Bosscher [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 17, 2007 2:52 PM
> To: Eric Weddington
> Cc: Kenneth Hoste; gcc@gcc.gnu.org
> Subject: Re: GCC -On optimization passes: flag and doc issues
>
> On 4/17/07, Eric Wedd
> -Original Message-
> From: Steven Bosscher [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 17, 2007 2:52 PM
> To: Eric Weddington
> Cc: Kenneth Hoste; gcc@gcc.gnu.org
> Subject: Re: GCC -On optimization passes: flag and doc issues
>
> On 4/17/07, Eric Wedd
> -Original Message-
> From: Ian Lance Taylor [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 17, 2007 4:20 PM
> To: Eric Weddington
> Cc: 'Steven Bosscher'; gcc@gcc.gnu.org; 'Joerg Wunsch';
> 'Anatoly Sokolov'
> Subject: Re: GCC -On
> -Original Message-
> From: Mike Stump [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 17, 2007 4:28 PM
> To: Eric Weddington
> Cc: 'Steven Bosscher'; gcc@gcc.gnu.org; 'Joerg Wunsch';
> 'Anatoly Sokolov'
> Subject: Re: GCC -On opti
increase code size? I feel I must be missing something really
obvious... is
it just that the other optimisations that become possible on inline
code
usually compensate?
That or the savings from not having to save/restore registers, set up
the frame, etc as well.
-eric
1 - 100 of 1857 matches
Mail list logo
