Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Recent xserver-kdrive failure and util-macros update
Date: Wed, 04 Jan 2012 12:08:58 -0800	[thread overview]
Message-ID: <4F04B1DA.7020503@linux.intel.com> (raw)
In-Reply-To: <4F04AC44.5000207@mlbassoc.com>

On 01/04/2012 11:45 AM, Gary Thomas wrote:
> On 2012-01-04 10:39, Khem Raj wrote:
>> On (03/01/12 23:28), Saul Wold wrote:
>>>
>>> We seem to have a relatively new failure in xserver-kdrive, which
>>> appeared in the last set of change. I tried to run though a bisect
>>> but was not able to find the problem.
>>>
>>> The problem seems to be related to configure.ac setting of
>>> XSERVER_CFLAGS='$(CWARNFLAGS)' and then using -Werror=address, which
>>> is what causes the failure.
>>>
>>> This seems to be related to the util-macros update to 1.16, which
>>> adds more warnings to errors. Since we are still using the older
>>> xserver-kdrive, there are warnings that are now errors with the
>>> update.
>>
>> Fix xserver-kdrive
>
> In this case, I don't see why this is an error. All of the errors
> (that I've found so far) stem from lines like this:
> REGION_INIT(pGC->pScreen, &rgnDst, &box, 1);
>
Not all, the newer code has this snippet as a static inline and does not 
have the failure because it a function.

There's at least one place that it's called with a real pointer in a 
function.

Sau!

> where the macro REGION_INIT is defined as:
>
> #define REGION_INIT(_pScreen, _pReg, _rect, _size) \
> { \
> if ((_rect) != NULL) \
> { \
> (_pReg)->extents = *(_rect); \
> (_pReg)->data = (RegDataPtr)NULL; \
> } \
> else \
> { \
> (_pReg)->extents = miEmptyBox; \
> if (((_size) > 1) && ((_pReg)->data = \
> (RegDataPtr)xalloc(REGION_SZOF(_size)))) \
> { \
> (_pReg)->data->size = (_size); \
> (_pReg)->data->numRects = 0; \
> } \
> else \
> (_pReg)->data = &miEmptyData; \
> } \
> }
>
> This doesn't look like an error to me, but rather an opportunity
> (to remove never used code).
>



  reply	other threads:[~2012-01-04 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04  7:28 Recent xserver-kdrive failure and util-macros update Saul Wold
2012-01-04  8:24 ` Xiaofeng Yan
2012-01-04 10:18   ` Cui, Dexuan
2012-01-04 17:39 ` Khem Raj
2012-01-04 19:45   ` Gary Thomas
2012-01-04 20:08     ` Saul Wold [this message]
2012-01-04 20:36       ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F04B1DA.7020503@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox