search for: gmacro

...m /usr/include/glib-2.0/glib.h:30, from /usr/include/glib-2.0/gobject/gbinding.h:28, from /usr/include/glib-2.0/glib-object.h:22, from /usr/include/libosinfo-1.0/osinfo/osinfo.h:28, from libosinfo-c.c:25: /usr/include/glib-2.0/glib/gmacros.h:1028:49: error: redefinition of 'glib_autoptr_clear_OsinfoList' 1028 | #define _GLIB_AUTOPTR_CLEAR_FUNC_NAME(TypeName) glib_autoptr_clear_##TypeName | ^~~~~~~~~~~~~~~~~~~ /usr/include/glib-2.0/glib/gmacros.h:1044:36: note: in expansi...

...lib.h:30, > from /usr/include/glib-2.0/gobject/gbinding.h:28, > from /usr/include/glib-2.0/glib-object.h:22, > from /usr/include/libosinfo-1.0/osinfo/osinfo.h:28, > from libosinfo-c.c:25: > /usr/include/glib-2.0/glib/gmacros.h:1028:49: error: redefinition of 'glib_autoptr_clear_OsinfoList' > 1028 | #define _GLIB_AUTOPTR_CLEAR_FUNC_NAME(TypeName) glib_autoptr_clear_##TypeName > | ^~~~~~~~~~~~~~~~~~~ > /usr/include/glib-2.0/glib/gmacros.h:1044:36: n...

...on project is" voice over ip" and i want to make codec to voice with speex-1.1.12 , i try to run it in my computer by" visual studio 6" but i have problems 1-i want to get exe file to speexdec&speexenc(i found missing files "glib.h, glibconfig.h, o gg/ogg.h, glib/gmacros.h , ogg_static.dsp" when i found it i have errors in the speexenc.c or speexdec) 2-i want enter voice file to test it in my computer thanks for your help Ahmed Gamil --------------------------------- Yahoo! Mail Bring photos to life! New PhotoMail makes sharing a breeze. ------...

Greetings everybody! I've created a patch to get compiz (upstream about 2 hours old) away from libsvg and libsvg-cairo. Those two libraries, which are regarded as "dead meat" by their initial developer Carl Worth, are replaced with librsvg 2.14.x (e.g. part of Gnome 2.14.x) by this patch. The patch is rather small and only touches these three files: compiz/configure.ac

...al. In addition, the DICompileUnit will contain a new optional field of macro list of type (MacroNodeArray). Finally, I assume that macro support should be disabled by default, and there should be a flag to enable this feature. I would say that we should introduce a new specific flag, e.g. "-gmacro", that could be used with "-g". [Example] Here is an example that demonstrate the macro support from Source->AST->LLVM IR->DWARF. Source ========================================================= mainfile.c: ------------------------------------------------------------------...

...e? In addition, the DICompileUnit will contain a new optional field of macro list of type (MacroNodeArray). Finally, I assume that macro support should be disabled by default, and there should be a flag to enable this feature. I would say that we should introduce a new specific flag, e.g. "-gmacro", that could be used with "-g". [Example] Here is an example that demonstrate the macro support from Source->AST->LLVM IR->DWARF. Source ========================================================= mainfile.c: ------------------------------------------------------------------...

...e? In addition, the DICompileUnit will contain a new optional field of macro list of type (MacroNodeArray). Finally, I assume that macro support should be disabled by default, and there should be a flag to enable this feature. I would say that we should introduce a new specific flag, e.g. "-gmacro", that could be used with "-g". [Example] Here is an example that demonstrate the macro support from Source->AST->LLVM IR->DWARF. Source ========================================================= mainfile.c: ------------------------------------------------------------------...

...e? In addition, the DICompileUnit will contain a new optional field of macro list of type (MacroNodeArray). Finally, I assume that macro support should be disabled by default, and there should be a flag to enable this feature. I would say that we should introduce a new specific flag, e.g. "-gmacro", that could be used with "-g". [Example] Here is an example that demonstrate the macro support from Source->AST->LLVM IR->DWARF. Source ========================================================= mainfile.c: ------------------------------------------------------------------...

...t will contain a new optional field of macro > list of type (MacroNodeArray). > > > > Finally, I assume that macro support should be disabled by default, and > there should be a flag to enable this feature. I would say that we should > introduce a new specific flag, e.g. "-gmacro", that could be used with > "-g". > > > > *[Example]* > > Here is an example that demonstrate the macro support from > Source->AST->LLVM IR->DWARF. > > > > Source > > ========================================================= > &gt...

...l field of macro >> list of type (MacroNodeArray). >> >> >> >> Finally, I assume that macro support should be disabled by default, and >> there should be a flag to enable this feature. I would say that we should >> introduce a new specific flag, e.g. "-gmacro", that could be used with >> "-g". >> >> >> >> *[Example]* >> >> Here is an example that demonstrate the macro support from >> Source->AST->LLVM IR->DWARF. >> >> >> >> Source >> >> ==========...

...o list of type (MacroNodeArray). >>> >>> >>> >>> Finally, I assume that macro support should be disabled by default, and >>> there should be a flag to enable this feature. I would say that we should >>> introduce a new specific flag, e.g. "-gmacro", that could be used with >>> "-g". >>> >>> >>> >>> *[Example]* >>> >>> Here is an example that demonstrate the macro support from >>> Source->AST->LLVM IR->DWARF. >>> >>> >>>...

A couple weeks ago I sat down with David Blaikie to figure out what we could trim when importing debug metadata during function importing. I have a prototype that reduces the resulting .o sizes significantly with ThinLTO -g. However, I ran into some issues when cleaning up part of this in preparation for a patch. Since Mehdi indicated that he and Adrian were going to be looking at this as well

...t needed in the importing module: change to nullptr > > Seems reasonable for -flto=thin (incorrect for -flto=full, though). > > > b) List of macros > > - Not needed in the importing module: change to nullptr > > We don't have macros by default, right? You need some -gmacros flag I > hope? I remember objecting to the massive debug info bloat when they were > introduced, but was convinced by an argument along the lines of > "it's-never-going-to-be-on-by-default". > Yes, it's off by default, but still good to think about whether we could...

...Right, all this is for ThinLTO - I haven't thought about Full LTO as I am concerned about ThinLTO importing-specific bloat. > > > b) List of macros > > - Not needed in the importing module: change to nullptr > > We don't have macros by default, right? You need some -gmacros flag I > hope? I remember objecting to the massive debug info bloat when they were > introduced, but was convinced by an argument along the lines of > "it's-never-going-to-be-on-by-default". > No I haven't seen a case where this is non-null in my ThinLTO testing, bu...