gcc algol 60 milestone 2

[Petr Machata]

Hi list!

For those interested, GCC Algol 60 project, the byproduct of GCC
Frontend Howto diploma thesis, still lives, and its second milestone is
available:

http://projects.almad.net/gcc-algol/wiki/Milestones

Thanks,
PM

Re: Enable EBX for x86 in 32bits PIC code

[Petr Machata]

Jakub Jelinek  writes:

> look at the sizes of .debug_info/.debug_loc sections with/without the
> patch, or use the locstat utility from elfutils

Not actually part of elfutils, but available either here:
https://github.com/pmachata/dwlocstat

... or packaged in Fedora.

Thanks,
PM

algol 60 for gcc

[Petr Machata]

Hi list!

I picked a diploma thesis assignment to implement a gcc frontend, and
document the process thoroughly. I chose Algol 60 as the language to
implement. There has already been one attempt to do Algol 60 frontend,
but it probably died:
  http://gcc.gnu.org/ml/gcc/2002-05/msg00432.html

>From my investigation so far, it seems that there is not that much to
document, apart from "read this buch of links and you're basically done;
the rest changes so rapidly it doesn't make sense to document".  But the
assignment is in place, so I will do my best to create something worth
reading.  In particular, I was looking at GCC documentation assignments:
  http://gcc.gnu.org/projects/documentation.html
and I think my work could be useful for "fully document the interface of
front ends to GCC".

I'm trying to make the university to GPL the code and documentation, and
give up their copyright, so that it could be used without restriction,
but won't know the outcome until later this year.

gcc-algol project site is here, for those interested:
  http://projects.almad.net/gcc-algol

Thanks,
PM

Re: algol 60 for gcc

[Petr Machata]

David Nicol wrote:
> On 8/8/06, Petr Machata <[EMAIL PROTECTED]> wrote:
> 
>> I'm trying to make the university to GPL the code and documentation, and
>> give up their copyright, so that it could be used without restriction,
>> but won't know the outcome until later this year.
> 
> I am not a lawyer, but my understanding from researching university
> claims to copyright of student work is that a university policy of
> holding a copyright on work you have done in a class that you paid to
> be in is entirely specious.
> 
> If you are being compensated for your work and receiving research
> grants or something like that it's different, but if you are doing
> work for a class that you are paying to be in, that work is yours
> under the Berne convention, and it is yours to license how you
> please. As a paying student, you hire your university to coach you.

Well, that makes sense, and I'm glad to hear that.  It's just that the
person that was answering my email was unsure, and told me that at the
beginning of the semester the things would get sorted out.  I was
looking into Czech Copyright Act just now, and it seems to me that
university indeed can't prevent me from disposing with the work, unless
I sign something stupid.  Let's see, I believe it'll come right.

> http://www.google.com/search?q=copyright+on+student+work
> shows many links to various policy documents, most of which refer to
> international copyright law, which should apply to FIT BUT as well as
> they apply in Canada or Minnesota.

Thanks,
PM

gcc algol 60 milestone 1

[Petr Machata]

Hi list!

For those interested, GCC Algol 60 project, the byproduct of GCC
Frontend Howto diploma thesis, still lives, and its first milestone is
available:

http://projects.almad.net/gcc-algol/wiki/Milestones

Thanks,
PM

Re: [boost] lots of warning with gcc-4.8.1 + boost-1.54.0

[Petr Machata]

Nathan Ridge  writes:

>> On 3 July 2013 02:41, Nathan Ridge wrote:
 ./boost/bind/arg.hpp:37:22: warning: typedef ‘T_must_be_placeholder’ 
 locally
 defined but not used [-Wunused-local-typedefs]
>>
>> It was new in GCC 4.7, http://gcc.gnu.org/gcc-4.7/changes.html
>
> I've seen spews of that warning for other large projects, such as
> clang or wxWidgets, not just boost.
>
> Would GCC consider removing it from -Wall?

GCC doesn't emit this warning if such typedefs are annotated with
__attribute__((__unused__)).  We just need to fix all instances of this
problem.  So far I identified these there:

- https://svn.boost.org/trac/boost/ticket/8844 (Boost.Bind)
- https://svn.boost.org/trac/boost/ticket/8847 (Boost.ConceptCheck)
- https://svn.boost.org/trac/boost/ticket/8859 (Boost.Serialization)

Thanks,
PM