diff options
| author | Marek Olšák <maraeo@gmail.com> | 2010-06-14 01:20:14 +0200 |
|---|---|---|
| committer | Marek Olšák <maraeo@gmail.com> | 2010-06-14 12:46:38 +0200 |
| commit | 1c0e5ba9f14ec297cbd5055ea402989b2cc71b8d (patch) | |
| tree | 7add5dd37414c193b17361ec1f58ce6fcc0ec1ef /src/gallium/drivers/r300/r300_cs.h | |
| parent | cf3778bae03460325960d2aec0cd4cdf325299eb (diff) | |
r300g: drop begin_cs/end_cs
I have had a look at the libdrm sources and they just contain more or less
the same checking we do in macros, and begin_cs may realloc the CS buffer
if we overflow it, which never happens with r300g. So these are pretty
much useless.
There is a small but measurable performance increase by dropping the two
functions.
Diffstat (limited to 'src/gallium/drivers/r300/r300_cs.h')
| -rw-r--r-- | src/gallium/drivers/r300/r300_cs.h | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/gallium/drivers/r300/r300_cs.h b/src/gallium/drivers/r300/r300_cs.h index 0baa20f08d..030fad3772 100644 --- a/src/gallium/drivers/r300/r300_cs.h +++ b/src/gallium/drivers/r300/r300_cs.h @@ -52,15 +52,12 @@ #define BEGIN_CS(size) do { \ assert(r300_check_cs(cs_context_copy, (size))); \ - cs_winsys->begin_cs(cs_winsys, (size), \ - __FILE__, __FUNCTION__, __LINE__); \ CS_DEBUG(cs_count = size;) \ } while (0) #define END_CS do { \ CS_DEBUG(if (cs_count != 0) \ debug_printf("r300: Warning: cs_count off by %d\n", cs_count);) \ - cs_winsys->end_cs(cs_winsys, __FILE__, __FUNCTION__, __LINE__); \ CS_DEBUG(cs_count = 0;) \ } while (0) @@ -143,7 +140,6 @@ * Command buffer emission. */ -/* It's recommended not to call begin_cs/end_cs before/after this macro. */ #define WRITE_CS_TABLE(values, count) do { \ CS_DEBUG(assert(cs_count == 0);) \ cs_winsys->write_cs_table(cs_winsys, values, count); \ |