, working on GNU and other Free Software
(the Kawa project is still going strong, and my job at Sun
is also Free Software). If you any questions about code I've
written - or just want to say "hi!" - feel free to contact me.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
J.C. Pizarro wrote:
Your idea with JavaScript, CSS, XSLT, .. is very good! :)
Thanks you - but ideas are cheap. Turned a vague idea into
something useful is a different matter
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
to switch between display styles. This can be
done dynamically with a smidgen of JavaScript.
* Can more easily convert to other formats, or select only desired
elements, using some suitable XML processor such as xsltproc.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
don't consistently monitor the gcc mailing lists, so please
cc me on any gcc email you want me to see in a timely manner.)
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
-gap, you could probably just remove setting and testing
the flag. That may introduce some regressions in terms of not
catching some errors.
A cleaner fix may be to create the PARAM_DECL at parse time, and set
the final flag on the decl, but that's a bigger change not worth
doing at this poi
ake a look at the other
(non-pch-related) regressions. We all have too many things on our
plates, so if someone else would like to pitch in, just let us know.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
which is normally the
index of the line_map of that included this line_map: i.e. the outer
line_map in the include stack. It seems plausible to generalize the
"included_from" field to also be used for "expanded from" or
"instantiated from", but I haven't tried to think through that.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
00882.html
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
ing internal source location to back-end
representation at tree conversion time, which seems to be
your preference, then I don't understand your point.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
n and I talked about it, but I don't know if he's
available. Worst case, I guess I could steal the time to do it,
but if nothing else it would be good to get more people
comfortable with how this all works.
And of course Ada needs MAPPED_LOCATION support.
--
--Per Bo
over that size.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
time check,
using reflection.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
les.
The "SourceDebugExtension" attribute specified by JSR-45
(http://jcp.org/en/jsr/detail?id=45) provides one way to
provide full pathnames.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
only useful if we also make
available a bytecode version of libgcj, I think.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
Tom Tromey wrote:
"Per" == Per Bothner <[EMAIL PROTECTED]> writes:
Per> A type attribute is much more useful. For example it allows:
Per> String x = shared ? "x" : new String("x");
Per> // The type of x [in a single-assignment-world] is non-null.
eally the compiler should realize that x actually has
the more specific type 'int __attribute__((never_null)) *', and
should use that information to generate better code. It seems
this should be straightforward using SSA, as I sketched in my
previous message.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
s_never_returns_NULL();
< ... use p without modifying it ... > <-- p_1 never NULL here.
}
else
{
int *p_2 = other_fn ();
< ... use p without modifying it ... > <-- p_2 may be NULL here.
}
int *p_3 = PHI(p_1, p_2);
... more uses of p ...;
}
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
Per Bothner wrote:
A "function-never-returns-null" attribute doesn't seem like
the right mechanism. Instead, there should be a "never-null"
attribute on pointer types. A "function-never-returns-null" is
just a function whose return-type has the "ne
Diego Novillo wrote:
On Saturday 12 November 2005 12:05, Per Bothner wrote:
A "function-never-returns-null" attribute doesn't seem like
the right mechanism. Instead, there should be a "never-null"
attribute on pointer types. A "function-never-returns-null&qu
.
A type attribute is much more useful. For example it allows:
String x = shared ? "x" : new String("x");
// The type of x [in a single-assignment-world] is non-null.
[If we already have such a mechanism, I apologize.]
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
iew the patches.
Per, there's one preprocessor patch below; would you please take a look?
The rest are middle-end patches.
Preprocessor
22042
I don't know enough about fine points of the standard to say what is
right. If you and Andrew think it is right, I'm ok with it.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
(another) fork
in their code-base. It means that Apple can produce a patch with
reasonable assurance that it will be approved (assuming we also get
consensus from the global write maintainers on the -Wcomment changes.)
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
y they can turn it off.
That would appear not to
solve the problem of the customers who are wedded to their line art,
that started this discussion in the first place.
They can use -Wno-comment.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
Joe Buck wrote:
On Sat, Oct 29, 2005 at 03:45:33AM -0700, Per Bothner wrote:
1. Change the behavior (back) so only '\\$', not '\\ *$', causes a
line to be continued.
The problem with your item #1 is that there is then no way of flagging
code that won't work
tespace.
3. Make -Wcomment the default - not just for -Wall, but always.
It can be turned off with -Wno-comment
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
pilers", as along as a warning is
emitted. The warning can be turned off with our generic
turn-off-specific-warnings framework (I'm so out of gcc
development I'm not sure we have one - but I vaguely
remember reading about it). However, the warning should be
on by default.
--
over the years!
Tom, please add yourself to the MAINTAINERS file.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
there is an aliasing bug somewhere?
I really would welcome someone else looking at one or more
of these, as I'm really behind on other (paying) projects.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
haven't no idea what regressions there might be. I'll at least do
a bootstap+check run to get a feel for the status.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
th:
if (frobbed)
warning (OPT_Wfoo, "foo is frobbed");
Perhaps a macro should be defined:
maybe_warning (OPT_Wfoo, frobbed, "foo is frobbed");
This tests whether Wfoo is enabled *before* it evaluates frobbed.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
utput.c so line 0
is printed as line 1.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
t it seems unlikely. I'll check that -fpreprocessed
doesn't break (I assume the testsuite tests this?), and I'll ask
someone to check distcc.
Objections to this approach? Other suggestions? One alternative is
to fix gas to not complain about line number 0.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
ed.
It semi-supports it. I build Kawa one directory at a time, using
libtool. (Albeit the CVS version of libtool.)
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
making --disable-static the default.
Building static libraries is not very useful on other than
embedded-class systems.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
t increase virtual memory use.
I think the net benefit could be large - an experiment would be
quite worthwhile. Perhaps somebody could write a post-configure
script to munge the Makefile and give us some numbers.
Ideally, there'd be a configure flag to control "chunking".
--
it didn't fit well with gdb's obstack-based memory management.
The situation might be different now.
OTOH, just like we now use Dwarf2 unwind-info for exception handling,
perhaps we could use Dwarf debug information for reflection information.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
s what is happening in PR 20907.
> This is PR 20907.
I have a patch I'll check in after testing.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
Per Bothner wrote:
However, the Kawa testsuite fails, raising a ClassNotFoundException.
I'm looking into it.
Hm. This fails, with or without the patch:
clas = Class.forName(cname);
This works:
clas = Class.forName(cname, true, getClass().getClassLoader());
This is with make all &a
Per Bothner wrote:
2005-04-02 Mark Wielaard <[EMAIL PROTECTED]>
* java/lang/natRuntime.cc (insertSystemProperties): Set
java.class.path to CLASSPATH if not already set.
Yes, Kawa builds with this patch. Thanks!
However, the Kawa testsuite fails, raising a ClassNotFoundExc
ath to CLASSPATH if not already set.
Yes, Kawa builds with this patch. Thanks!
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
elard said he's looking into the problem. Unfortunately,
we haven't heard anything from Tom Tromey, the auther of the big
patch that probably causes the problem.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
:
$ gcj -o CL CL.java --main=CL
$ CLASSPATH=.:/:/usr:/random ./CL
gnu.gcj.runtime.SystemClassLoader{urls=[file:./],
parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
(Of course to be picky "file:/usr/" is not a valid URL ...)
--
--Per Bothner
[EMAIL PROTECT
Per Bothner wrote:
I can no longer build Kawa using the 4.0 branch.
Some more information:
The failing statement is:
Class.forName("kawa.lib.prim_syntax", false,
getClass().getClassLoader());
prim_syntax.class exists in the current directory,
which is ../../kawa/lib. The
the CLASSPATH.
That suggests it might be related to Tom's check-in.
I'll track it down a little bit further.
This is on Fedora Core 3, x86.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
non-gc'd memory to
gc'd memory will be a dangling pointer, if we count static variables
marked with GTY as "gc'd memory" in this context.
Right now, as far as I can tell, the filenames in the line_table are
allocated from non-gc'd memory. This complicates usi
to split those
into two separate arrays: an array of (const char*) and an array
of non-relocatable data. I don't know if that would be helpful.
It would means fixing client code that references map entries
directly.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
e (probably not a big
deal - cpplib accesses are via the cpp_reader and thus unchanged).
But note we still need custom restore code.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
7;t know dejagnu, I've forgotten most of what little I
used to know about tcl, and I don't know where to start. I'm asking
for someone who will know the Right Thing, and who will do.
Anyone out there?
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
at's in the eye of the beholder. I think a local translation
is cleaner and more robust/safer than a global opaque type/call-back.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
r Ada, but I don't think it's the best long-term solution for Gcc
as a whole.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
doesn't mention how to run the testsuite. Perhaps there should be a
link to http://gcc.gnu.org/install/test.html from the internals
manual.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
t the basics);
- the "Testsuite Conventions" of codingconventions.html;
- contribute.html;
- install/test.html;
- and of course Google.
In *none* of these did I find documentation on how to write or
understand a test-case, or a link to such documentation. I'm inclined
to think that most of
at extensible?
In any case, using the client's LC_COLLATE may not be the right thing,
and it's certainly not important.
(I believe someone is working on it to some degree, soon)
Great.
As I said: I don't see this issue as a show-stopper for converting
gcc to svn.
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
Andreas Schwab wrote:
Per Bothner <[EMAIL PROTECTED]> writes:
Preferably, the sort algorithm should match 'ls'. (Specifically
GNU ls - IIRC BSD ls doesn't case-fold, which I think is wrong.
The sort alghorithm has nothing to do with ls, but with your selection of
LC_COLLA
svn output is not by
default in a predictable output, that is most definitely a serious
(but not critical) bug. (It's ok to have a "don't sort" option to
speed things up, but it shouldn't be the default.)
--
--Per Bothner
[EMAIL PROTECTED] http://per.bothner.com/
56 matches
Mail list logo
