[Bug other/42541] New: [PATCH] install except.h libfuncs.h version.h (plugin headers)

[rmh dot gcc at aybabtu dot com]

Please could you install except.h libfuncs.h version.h in the plugin header
directory?  They're necessary for building dragonegg.


-- 
   Summary: [PATCH] install except.h libfuncs.h version.h (plugin
headers)
   Product: gcc
   Version: 4.5.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: other
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rmh dot gcc at aybabtu dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42541

[Bug other/42541] [PATCH] install except.h libfuncs.h version.h (plugin headers)

[rmh dot gcc at aybabtu dot com]

--- Comment #1 from rmh dot gcc at aybabtu dot com  2009-12-29 15:59 ---
Created an attachment (id=19415)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19415&action=view)
makefile patch


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42541

[Bug c/42537] [PATCH] misc spelling fixes

[rmh dot gcc at aybabtu dot com]

--- Comment #4 from rmh dot gcc at aybabtu dot com  2009-12-29 16:03 ---
Mail to gcc-patches sent.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42537

[Bug c/42579] New: [PATCH] support for obtaining file basename

[rmh dot gcc at aybabtu dot com]

Please consider this patch.  It adds support for obtaining file basename via
__FILE_BASENAME__.

This would be used by GNU GRUB.  I'll provide some explanation on why this is
very necessary for us:

  - Bootloader code is very critical; a bug can render system unbootable. 
Additionally, it needs to support a wide range of hardware and firmware. 
Because of this, we put extensive debugging support into GRUB.  Debug
statements currently rely on __FILE__.

  - We want to support $srcdir != $objdir build setups, and continue supporting
them.

  - Some parts of bootstrap code tend to be very size constrained.  Every byte
counts, and each debug statement is taking unnecessary space because accessing
a file in $srcdir requires either an absolute path or at least a number of
'../' components (in Debian, that would be two of them).

Because of this, I would find it very useful if GCC provided __FILE_BASENAME__,
or at least an equivalent facility.


-- 
   Summary: [PATCH] support for obtaining file basename
   Product: gcc
   Version: 4.5.0
Status: UNCONFIRMED
  Severity: enhancement
  Priority: P3
 Component: c
AssignedTo: unassigned at gcc dot gnu dot org
    ReportedBy: rmh dot gcc at aybabtu dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42579

[Bug c/42579] [PATCH] support for obtaining file basename

[rmh dot gcc at aybabtu dot com]

--- Comment #1 from rmh dot gcc at aybabtu dot com  2010-01-02 10:12 ---
Created an attachment (id=19445)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19445&action=view)
__FILE_BASENAME__

Attaching the patch.  Also sent to gcc-patches.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42579

[Bug c/42579] [PATCH] support for obtaining file basename

[rmh dot gcc at aybabtu dot com]

--- Comment #3 from rmh dot gcc at aybabtu dot com  2010-01-02 11:39 ---
(In reply to comment #2)
> __BASE_FILE__ could be enough for what you want.

Hi,

I tried already, but __BASE_FILE__ seems to be something unrelated.  It's
like __FILE__ but when used in an #include'd source it picks the includer
rather than the included file.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42579