All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76009] New: r600_streamout.c:108:6: error: conflicting types for 'r600_set_streamout_targets'
Date: Tue, 11 Mar 2014 04:24:33 +0000	[thread overview]
Message-ID: <bug-76009-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2387 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=76009

          Priority: medium
            Bug ID: 76009
          Keywords: regression
                CC: jfonseca@vmware.com, maraeo@gmail.com,
                    sroland@vmware.com, zackr@vmware.com
          Assignee: dri-devel@lists.freedesktop.org
           Summary: r600_streamout.c:108:6: error: conflicting types for
                    'r600_set_streamout_targets'
          Severity: blocker
    Classification: Unclassified
                OS: Linux (All)
          Reporter: vlee@freedesktop.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

mesa: dfa25ea5cd19d5a050a1c94bd7370a2259b9f007 (master 10.2.0-devel)

  CC       r600_streamout.lo
r600_streamout.c:108:6: error: conflicting types for
'r600_set_streamout_targets'
 void r600_set_streamout_targets(struct pipe_context *ctx,
      ^
In file included from r600_streamout.c:27:0:
r600_pipe_common.h:413:6: note: previous declaration of
'r600_set_streamout_targets' was here
 void r600_set_streamout_targets(struct pipe_context *ctx,
      ^

dfa25ea5cd19d5a050a1c94bd7370a2259b9f007 is the first bad commit
commit dfa25ea5cd19d5a050a1c94bd7370a2259b9f007
Author: Zack Rusin <zackr@vmware.com>
Date:   Thu Mar 6 18:43:44 2014 -0500

    gallium: allow setting of the internal stream output offset

    D3D10 allows setting of the internal offset of a buffer, which is
    in general only incremented via actual stream output writes. By
    allowing setting of the internal offset draw_auto is capable
    of rendering from buffers which have not been actually streamed
    out to. Our interface didn't allow. This change functionally
    shouldn't make any difference to OpenGL where instead of an
    append_bitmask you just get a real array where -1 means append
    (like in D3D) and 0 means do not append.

    Signed-off-by: Zack Rusin <zackr@vmware.com>
    Reviewed-by: Roland Scheidegger <sroland@vmware.com>
    Reviewed-by: Jose Fonseca <jfonseca@vmware.com>
    Reviewed-by: Marek Olšák <marek.olsak@amd.com>

:040000 040000 899aff75fb864562d50d09d1b72b728adfa3c9be
c1582db45fac19679419c7bcf4152269b630df36 M    src

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4179 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-03-11  4:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  4:24 bugzilla-daemon [this message]
2014-03-11  5:56 ` [Bug 76009] r600_streamout.c:108:6: error: conflicting types for 'r600_set_streamout_targets' bugzilla-daemon

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=bug-76009-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.