diff options
| author | Thomas Schwinge <tschwinge@gnu.org> | 2012-04-17 00:16:32 +0200 |
|---|---|---|
| committer | Thomas Schwinge <tschwinge@gnu.org> | 2012-04-17 00:16:32 +0200 |
| commit | 1dc28d745d45be6764072af1da0ceda52a0c17a3 (patch) | |
| tree | 1271b34236f2b2577185b11b1d2ade6fb1f0dbe8 /open_issues/extern_inline.mdwn | |
| parent | a65f14df8e3d93f71acf276fb0773d6557b9fbab (diff) | |
IRC.
Diffstat (limited to 'open_issues/extern_inline.mdwn')
| -rw-r--r-- | open_issues/extern_inline.mdwn | 39 |
1 files changed, 37 insertions, 2 deletions
diff --git a/open_issues/extern_inline.mdwn b/open_issues/extern_inline.mdwn index a56d4902..a3a22b16 100644 --- a/open_issues/extern_inline.mdwn +++ b/open_issues/extern_inline.mdwn @@ -1,4 +1,4 @@ -[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2010, 2012 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -10,7 +10,10 @@ License|/fdl]]."]]"""]] [[!tag open_issue_hurd]] -IRC, unknown channel, unknown date. +[[!toc]] + + +# IRC, unknown channel, unknown date <tschwinge> youpi: Did you ever review the Savannah hurd branch master-fix_extern_inline? <youpi> why static inlines instead of extern lines ? @@ -72,3 +75,35 @@ IRC, unknown channel, unknown date. <youpi> especially since the semantic has changed over time and according to standards :) <tschwinge> And then GCC changing that according to C99. <tschwinge> Yes. + + +# IRC, freenode, #hurd, 2012-03-14 + + <youpi> + http://anonscm.debian.org/gitweb/?p=pkg-hurd/hurd.git;a=blob;f=debian/patches/extern_inline_fix.patch;h=b9eacbff97dc56e99a69ddb601a5fc948f6e44a7;hb=HEAD + <youpi> maybe review it, and then we apply it + <pinotree> + http://patch-tracker.debian.org/patch/series/view/hurd/20120222-1/extern_inline_fix.patch + ;) + <civodul> youpi: the #ifdef __USE_EXTERN_INLINES in there and the extra + "extern" decls look wrong to me + <youpi> iirc USE_EXTERN_INLINES is needed + <youpi> otherwise it's not compliant + <youpi> or maybe it's for -O0 + <youpi> anyway IIRC it's needed + <civodul> when !defined __USE_EXTERN_INLINES, you end up with extern decls + with no corresponding definition + <youpi> yes + <youpi> they are defined in the code + <civodul> where? + <youpi> there's a special .c file in each lib + <youpi> libdiskfs/extern-inline.c + <youpi> etc + <civodul> oooh, right + <youpi> extern inline means that anyway + <youpi> the compiler is allowed to not always inline + <civodul> yes + <civodul> that looks good to me, then + <civodul> youpi: can you apply it, with proper authorship & co.? + <civodul> (no rush, though) + <youpi> sure |