We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Created attachment 1851 [details]
Small test program showing the behaviors found.

In my game, I want to create a texture by rendering other textures in a target texture (SDL_TEXTUREACCESS_TARGET), and then creating a SDL_TEXTUREACCESS_STATIC texture from it.

To do that, I:
create a texture with SDL_TEXTUREACCESS_TARGET,
set it as the render target, using SDL_SetRenderTarget 
render all my other textures over it,
use SDL_RenderReadPixels to get the pixel data back from it,
create a surface from this pixel data,
create a new texture from this surface,
free and clean up everything (but the resulting texture)

After trying to achieve that for some time, I noticed that all I could get was a black image.
Than I realized that, using direct3d as renderer, SDL_RenderReadPixels always returned something from the screen or black. After some research (I didn't have time to look at the code yet), I found 2 guys saying that on direct3d SDL_RenderReadPixels always reads from the backbuffer, it doesn't matter the texture set with SDL_SetRenderTarget.
Then I switched the driver to opengl to check the behaviour.  On opengl, the pixels from the texture set as renderTarget are retrieved, but in upside down order. I don't know if that is an expected behavior, but it doesn't looks like.

After that, I wrote a small test program that shows up this behaviours, which I'm attaching to this report.
 
Some "may be useful" info:
I'm running DirectX 11.0 here, on Windows 8.1, with a Nvidia GTX 670M with drivers updated.
I triple checked if my system supported renderTargets, just to be sure.