gbmap: Tried to adopt the gbmap name more consistently
Having gbmap/bmap used in different places for the same thing was confusing. Preferring gbmap as it is consistent with other gstate (grm queue, gcksums), even if it is a bit noisy. It's interesting to note what didn't change: - The BM* range tags: LFS3_TAG_BMFREE, etc. These already differs from the GBMAP* prefix enough, and adopting GBM* would risk confusion for actual gstate. - The gbmap revdbg string: "bb~r". We don't have enough characters for anything else! - dbgbmap.py/dbgbmapsvg.py. These aren't actually related to the gbmap, so the name difference is a good thing.
This commit is contained in:
+10
-10
@@ -47,8 +47,8 @@
|
||||
#ifndef LFS3_GC
|
||||
#define LFS3_GC
|
||||
#endif
|
||||
#ifndef LFS3_BMAP
|
||||
#define LFS3_BMAP
|
||||
#ifndef LFS3_GBMAP
|
||||
#define LFS3_GBMAP
|
||||
#endif
|
||||
#endif
|
||||
|
||||
@@ -83,8 +83,8 @@
|
||||
#ifdef LFS3_YES_GC
|
||||
#define LFS3_GC
|
||||
#endif
|
||||
#ifdef LFS3_YES_BMAP
|
||||
#define LFS3_BMAP
|
||||
#ifdef LFS3_YES_GBMAP
|
||||
#define LFS3_GBMAP
|
||||
#endif
|
||||
|
||||
// LFS3_NO_LOG disables all logging macros
|
||||
@@ -263,17 +263,17 @@
|
||||
#define LFS3_IFDEF_GC(a, b) (b)
|
||||
#endif
|
||||
|
||||
#ifdef LFS3_BMAP
|
||||
#define LFS3_IFDEF_BMAP(a, b) (a)
|
||||
#ifdef LFS3_GBMAP
|
||||
#define LFS3_IFDEF_GBMAP(a, b) (a)
|
||||
#else
|
||||
#define LFS3_IFDEF_BMAP(a, b) (b)
|
||||
#define LFS3_IFDEF_GBMAP(a, b) (b)
|
||||
#endif
|
||||
|
||||
// TODO other LFS3_IFDEF_YES_* macros?
|
||||
#ifdef LFS3_YES_BMAP
|
||||
#define LFS3_IFDEF_YES_BMAP(a, b) (a)
|
||||
#ifdef LFS3_YES_GBMAP
|
||||
#define LFS3_IFDEF_YES_GBMAP(a, b) (a)
|
||||
#else
|
||||
#define LFS3_IFDEF_YES_BMAP(a, b) (b)
|
||||
#define LFS3_IFDEF_YES_GBMAP(a, b) (b)
|
||||
#endif
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user